►
From YouTube: IETF101-TUTORIAL-GOODINTERNETDRAFT-20180318-1345
Description
GOODINTERNETDRAFT TUTORIAL at IETF101
2018/03/18 1345
https://datatracker.ietf.org/meeting/101/proceedings/
B
C
C
So
why
us
who
are
we
Spencer
is:
is
the
Wonder
hamster
and
I'm
the
old
dog
for
legacy
reasons
of
our
own
internet
domains
and
so
on?
Spencer
is
currently
serving
as
a
transport
area
director
and
has
done
so
for
the
last
five
years,
and
that
means
he
reviews
all
of
the
internet
drafts
that
are
produced
by
the
IETF.
So
he's
got
quite
a
wide
view
of
that
and
he's
been
around
even
longer
than
me,
which
is
why
his
beard
is
gray
and
mine.
C
Isn't
he's
done
lots
of
stuff
in
the
ITF
on
the
s3
he's
in
the
internet,
research
task
force
and
here
on
the
OAB
as
well?
Weren't
you
previously
yeah
yeah
I
have
just
been
appointed
as
independent
streams.
Editor
sorry
in
submissions
editor,
and
that
means
I'm
responsible
for
RFC's
come
outside
the
ITF
process.
I
was
six
years
on
the
s3.
As
the
original
area
director
and
I've
chaired
working
groups
across
sort
of
half
of
the
ITF
together
I
looked
it
up.
C
C
Fault
and
obviously,
because
of
our
time
on
the
is
G
we
have
reviewed
literally
thousands
of
internet
drafts.
So
what's
the
point,
what's
the
point
of
being
here?
What's
the
point
of
posting
an
internet
draft,
maybe
you've
got
an
idea,
you
won't
do
a
tf2,
a
dot.
Maybe
it's
something
you
want
to
get
published
as
an
RFC
to
influence
the
standards
that
govern
the
internet.
Maybe
it's
just
some
thoughts
that
you
want
to
share.
It's
it's
like
a
discussion
document.
C
Whatever
the
point
of
it
is
the
implication,
is
you
want
people
to
be
able
to
read
it
and
understand
it?
You
want
the
process,
the
publication
process
to
run
through
successfully,
and
that
may
be
through
the
is
G
or
the
IRT
F
of
the
IAB
or
the
ISE,
and
so
you
actually
need
to
get
that
the
people
responsible
for
that
publication
process
to
agree.
Yes,
this
has
to
be
published.
C
And,
lastly,
you
want
the
RFC
editor
team
to
actually
be
able
to
publish
it.
So
there's
a
publication
process
that
says
here's
the
document
now,
let's
turn
it
into
proper
English
and
format
it
correctly
and
get
it
out
there.
The
document
has
to
be
in
a
form
that
that
can
be
done
without
the
use
of
magic.
C
So,
let's
talk
through
the
basic
process,
steps
take
the
microphone
out
of
here.
So
I
can
see
the
side
which
I
can
probably
read,
and
you
probably
come
from
the
better
room,
but
there
we
are,
the
slides
are
online.
If
you
want
to
follow
along
that
way,
so
anyone
can
post
an
ID
right.
Anyone
there's
no
membership,
no
requirements.
All
you
have
to
do
is
format
it
and
give
it
to
the
submissions
tool,
there's
no
checks
on
the
quality
or
the
content
of
what's
posted.
C
C
C
Usually
the
working
group
chairs
go
and
poll
their
working
grit
and
say:
do
we
want
to
work
on
this?
Are
we
happy
and
some
working
groups
have
teams
of
reviewers
to
vet
the
documents
and
obviously
the
chairs
review
it
once
it's
adopted,
the
working
group
owns
the
draft
and
what
that
really
means
is
that
they
are
responsible
for
the
content.
So
be
aware,
you
have
your
favourite
idea,
the
best
idea
in
the
whole
world.
You
bring
it
to
a
working
group.
C
Then,
given
to
a
designated
shepherd,
often
motion
grip
chairs,
but
not
always,
and
they
produce
a
short
writer
and
asked
to
publication,
which
means
it
gets
handed
to
an
area
director
who
reviews
the
document
often
sends
it
to
their
own
Directorate
review
team
when
they're
happy.
It
goes
for
IETF
last
call,
and
that
involves
a
review
by
the
community
by
more
directorates
by
I,
honor
and
ultimately
by
the
whole
of
the
iesg
and
then
finally,
it
goes
to
the
RSC
editor,
who
performs
the
rather
important
copy
edit
function.
C
I
short
note
about
copyright
in
IPR
when
you
produce
a
draft
and
submit
it
there's
an
automatic
requirement
that
include
a
piece
of
boilerplate
text.
The
boilerplate
text
is
something
you
need
to
read
and
you
may
need
to
show
it
to
your
sponsoring
company's
legal
team
because
it
says
stuff
about
IPR
and
copyright.
I
am
NOT.
A
lawyer
and
I've
never
played
one
in
a
television
series,
but
I
do
know
that
this
text
says
that
you
are
making
a
personal
declaration
and
statement
to
the
IETF
about
IPR.
C
C
A
Couragous
add
one
of
the
definitions
of
not
political
and
so
favorably.
Is
that
you're,
not
you're
kind
of
saying
this
is
not
going
to
be
considered
for
standard,
is
a
for
a
standards
track.
So
this
is
now
that
this
isn't.
This
will
not
be
a
standard.
If
it,
you
know
you're.
Basically,
that's
the
the
bus.
You
got
off
of
by
doing
something
different.
C
So
the
the
standard
approach
in
the
software
industry
and
hopefully
is
now
properly
taught
in
computer
science
courses-
is
that
the
later
you
find
about
the
more
expensive
it
is
to
fix
so
finding
above
it,
specification
is
half
the
price
of
finding
above
design
and
it's
half
the
price
of
flying
reading
code
and
finding
it
in
the
field
is
really
expensive.
So
we
want
to
do
the
same
with
our
documents.
We
want
to
get
the
bugs
out
early
before
they've
caused
damage
and
before
people
have
become
emotionally
attached
to
what
they've
written
it's
remarkable.
C
C
C
C
C
The
style
guide
talks
about
two
things:
it
talks
about
the
sections
you
have
to
have
and
what
information
has
to
go
in
each
section
and
it
talks
about
some
basic
do's
and
don'ts
about
how
to
write
the
text
out
of
deep
Jannetty
of
bullet
points,
whether
to
write
in
slang
or
not
so
the
mandatory
stuff
for
sections
that
are
in
there
all
of
the
the
boilerplate.
That's
about.
C
Ipr
about
copyright
about
the
the
fact
that
internet
drafts
expire
every
six
months,
that's
got
to
be
present.
To
be
honest,
the
way
I
do
it
is
I,
go
and
look
at
the
most
recent
draft.
That
was
posted
and
passed
all
the
checks
and
copy
it,
but
you
can
get
a
lot
of
it
free
with
the
tools
you
have
to
have
a
security
consideration
section.
You
have
to
have
an
eye
on
a
consideration
section
and
we'll
talk
about
those
in
a
minute.
C
That
is
on
another
slide
as
well.
There
are
other
sections
that
may
be
helpful
implementation
status,
telling
people
you've
already
written
code,
and
it's
already
in
the
field
helps
people
know
how
to
take
what
you've
written
other
sections
that
people
might
say
are
needed
are
not
really
needed.
So
if
you
read
RSC
40:41,
it
suggests
you
should
have
morality,
consideration
section
you
don't
have
to
do
it.
C
You
should
do
it
you'll
be
struck
by
lightning.
If
you
don't
so
security,
it's
built
to
be
there
and
it
has
to
be
meaningful.
It
doesn't
have
to
be
there
from
day
one
or
it
can
be
empty
from
day
one,
but
by
the
time
you're
asking
for
working
group
last
call
it's
got
to
be
real.
It's
got
to
be
what
you
think
is
right,
so
don't
just
write
what
you
think
you
can
get
away
with
the
security
police
will
read
it
and
will
tell
you
you're
wrong,
think
about
it.
C
C
So
there's
lots
of
relevant
existing
security
documents
that
may
be
related
to
your
protocol.
You
can
go
out
and
you
can
look
at
if
you
go
to
the
MPLS
working
group
and
search
for
the
word.
Security
you'll
find
a
number
of
RFC's
that
are
relevant
for
MPLS.
So
that's
it
approach
talk
to
working
group
chairs.
They
should
know
existing
security,
work
related
to
your
area
of
work
and
then
look
at
some
Pierce's
there
are.
C
There
are
number
of
RFC's
that
give
guidance
on
how
to
write
security
sections,
how
to
think
about
security
and
privacy
go
to
the
security
Directorate.
A
security
Directorate
is
a
group
of
people
who
get
security
and
they
have
volunteered
their
time
to
review
stuff.
So
when
you've
written
your
draft
and
it's
yeah,
the
basic
protocol
is
there,
you
can
go
to
the
Directorate
and
say
help.
C
C
Iona
Iona
is
Ayana.
Considerations
is
another
mandatory
section
and
you
cannot
be
clear
enough.
Ok,
the
text
in
this
you
should
treat
as
if
you're,
giving
formal
protocol
instructions
to
a
protocol
engine,
even
though
the
person
who's
consuming.
It
is
a
human,
because
if
this
goes
wrong,
your
protocol
is
broken.
C
So
you
have
to
say
which
registries
be
precise,
which
registries
are
you
talking
about?
Use
the
name,
because
that
name
of
the
registry
don't
just
say:
there's
a
registry
for
protocol
bits
that
you
know
nail
it
down,
write
down
exactly
what
you
want
the
registry
to
say
when
the
changes
have
been
made,
don't
say:
oh
allocate
via
a
value,
say,
allocate
a
value
saying
this
is
its
name.
This
is
its
purpose,
is
the
reference
basically
cut
and
paste
from
the
registry
that
exists
into
the
draft
and
then
fill
in
what
you
want?
C
C
Big
bug
better
do
not
use
explicit
values
when
you
write
an
eye
on
a
section
for
an
existing
registry,
don't
do
it
unless
you've
done
early
allocation
or
you're
actually
creating
the
registry.
It's
not
your
job
to
put
values
in
there.
It's
Iona's
job
and
if
you
put
values
in
there,
you've
run
all
sorts
of
problems,
because
somebody
else
might
have
written
draft
also
putting
values
in
and
now
you've
got
contention.
The
whole
point
of
Ayane
is
to
sort
that
out
so
use
tags
conventionally
use,
TBD
and
identify
which
one.
C
Manageability
considerations:
it's
not
a
requirement
that
you
do
this,
but
you
know
honestly,
you
should,
because
you
want
your
protocol
to
get
used,
you
want
it
to
get
managed
properly
and
be
usable.
You
need
to
think
about
these
things
at
day.
One
an
absolute
classic
is
om.
Om
tends
to
get
left
out
of
protocols
right
the
way
through
until
they're
in
the
field,
and
then
it
has
to
be
reverse
engineered.
So
a
good
protocol
spec
starts
talking
about
manageability
early.
C
C
C
It's
a
it's
a
proof
that
the
document
describes
the
protocol
that
works.
It's
a
proof
that
there
is
readability
and
comprehension
of
your
document
and
it's
okay
to
say
that
the
end
of
this
nobody's
implemented
this
yet.
But
two
people
have
told
me
that
they
are
they're
really
planning
to.
It
is
just
dealing
extra
information.
C
Interestingly,
this
status
is
stripped
from
an
RFC
before
publication,
because
it's
reporting
on
on
a
snapshot.
It's
saying
this
is
where
we
are
in
the
process.
The
draft
is
here.
This
is
what's
been
done
when
the
RFC
is
published,
it's
archived
forever,
and
so
this
would
get
out
of
date
immediately.
So
it's
stripped
out.
E
C
C
So
when
there's
a
adoption,
it
needs
to
get
proper
review
in
the
right
working
group
and
that
maybe
multiple
working
groups
increasingly
we're
finding
drafts
Span
working
groups,
it's
easy
to
get
attention.
You
send
a
mail
to
multiple
mailing
lists,
done
if
you're
doing
writing
a
document
about
a
special
subject
that
crosses
areas
get
the
reviews
and
the
examples
that
I've
given
here
yang
security
management.
There
are
special
review
teams
out
there
to
help
get
this
right,
so
you
may
be
living
somewhere
in
the
internet
area.
Writing
a
young
model.
C
C
Classic
is
the
must:
may
should
etc,
etc,
language,
it
looks
kind
of
trivial,
but
it's
actually
quite
important
to
get
it
tight,
because
this
is.
This
is
almost
legal
language
for
the
interpretation
of
the
implementer
and
that
the
classic
is,
if
you
write
should
when
you
receive
this
packet,
you
should
do
this.
You
are
also
implying
that
there
is
a
may
do
something
else.
You
could
have
write
it
down.
Otherwise
people
will
just
say:
oh,
it's
assured
I,
don't
have
to
do
it.
C
If
it's
an
experiment,
if
you've
gone
for
an
experimental
RFC,
then
you
have
to
actually
describe
the
experiment.
How
will
I
know
if
this
experiment
is
a
success?
What
are
the
parameters
if
it
is
it
in
a
closed
garden?
Is
it
in
the
Internet
at
large
and
then,
lastly,
in
my
pet
knits
and
gripes
is
backwards
and
forwards
compatibility
if
you're
extending
a
protocol
or
you're
writing
a
a
new
protocol
to
replace
something
talk
about
how
that
interacts
with
what's
already
there
if
you're
writing
it,
any
protocol
talk
about
how
it
can
be
extended.
C
C
D
C
C
C
You,
then,
is
that
what
you
meant,
but
you
might
not
understand
what
they're
saying
so,
there's
a
there's,
a
real
danger
that
you
introduce
technical
errors
right
at
this
very
last
stage
of
edit,
and
some
of
that
is
because,
when
your
copy
editor
says
this
word
should
be
that
word.
You
say:
Oh
I
didn't
understand
that
because
I'm,
not
a
native
speaker,
so
let's
change
it
and
then
you
actually
change
the
meaning
so
use
resources.
C
C
You
can
talk
to
other
people
in
the
working
group
and
there
are
actually
usually
in
working
groups,
quite
a
lot
of
people
who
are
keen
to
get
involved.
They
want
to
help.
So
if
you
say
well,
I've
got
this
draft
I'd
like
somebody
to
review
it
for
me
for
English,
then
you'll
get
answers
and
then
look
at
the
RFC
editor
pages
for
various
working
workshop,
outputs
and
advice
on
writing
ideas
and
there's
some
links
there
and
lastly,
there's
an
online
spell
checker
for
internet
drafts.
It's
not
got
a
perfect
dictionary,
but
it's
pretty
good.
C
Good
I
do
spell
and
I
think
it's
another
of
Henrichs
wonderful
tools.
Excellent,
so
I've
got
just
a
few
more
slides
before
handing
over
to
Spencer
diagrams.
Okay,
it's
your
writing
text,
but
do
diagrams
diagrams
really
help
make
them
simple,
diagrams.
It's
nice
and
easy
to
understand
a
clear
diagram.
Modern
artists
is
harder
to
understand.
Ask
the
art
actually
drawing
pictures
in
ASCII
is
not
a
natural
thing.
Some
people
can
just
do
it.
Some
people
can't
don't
worry.
If
you
find
it
hard
get
somebody
to
help.
C
C
D
C
If
you
want
to
see
what
that
future
is
going
to
look
like
with
SVG
and
so
forth,
there's
a
FAQ
on
the
RSC
editor
web
page,
which,
which
tells
you
all
you
need
to
know
so.
I,
went
and
looked
at
a
random
picture.
I
might
know
how
this
looks
from
the
back
of
the
room
yeah.
It
looks
as
bad
as
it
looks
on
my
laptop.
C
So
this
is
this
is
a
really
good
example
of
you
know
what
not
to
do.
There
are
circles
there
are
kind
of
where
all
the
lines
made
up
of
zeros
or
o's,
so
why?
Why
is
that?
That's
just
not
a
simple
line
and
then
there's
some
random
floating
characters
in
there
as
well.
So
if,
when
you've
drawn
it,
it
doesn't
look
good,
you
know
what
it's
not
good,
but
you
can
do
as
RFC
81
14
shows
you.
A
C
Mine
are
real
uniforms,
since
it's
just
a
two-dimensional
one
right
did
you
say
what
you
meant
to
say?
Okay,
not
just
is
it
clear,
but
is
it
clearly
what
he
meant
to
say
so,
a
knowledgeable
reviewer
and
a
friendly
one,
willpower's
confusing
texts
sympathetically?
And
if
you
wrote
it
yourself,
you
maybe
don't
even
notice,
it's
confusing,
because
it
says
what
you
really.
You
wrote
it,
so
you
know
what
it
means.
C
Try
to
think
about
it.
From
the
perspective
of
a
newcomer,
somebody
who
doesn't
know
the
topic
very
well
and
has
picked
up
your
draft
for
the
first
time.
Will
it
be
clear?
So
sometimes
the
issues
are
our
emulation.
We've
talked
about.
Sometimes
it's
writing
style
short
sentences
are
good,
but
writing.
A
complex
short
sentence
is
bad,
so
my
advice
is
normally
use
more
words
but
keep
the
sentences
short
use
bullet
points,
but
it
points
really
help
and
don't
use
the
passive
voice,
or
rather
the
passive
voice
should
not
be
used.
C
We've
also
talked
about
our
sc2
and
1/9
language,
so
ask
the
reviews:
ask
for
more
reviews,
ask
for
more
reviews
and
then
run
it
through
the
last
calls
and
get
everybody
to
look
at
it.
Probably
that
list
should
really
highlight
ask
for
reviews
from
friends.
They
don't
even
have
to
be
technically
knowledgeable
friends.
C
They
may
be
working
in
a
different
area
of
the
ATF,
but
you
met
them
over
a
beer
and
you'd
like
some
help
asked
for
help
and
I
picked
an
abstract
from
a
draft,
and
this
is
not
to
get
at
the
person
concerned.
So
I
picked
one
from
somebody
who
works
same
company
as
me,
and
you
can
try
to
read
this
and
pause
it
in
your
own
time,
but
basically
about
halfway
through
this
abstract
I
when
I
first
read
it
I
felt
I'm
drowning
I
have
no
idea
of
what
this
is
talking
about.
C
C
Yeah,
why
have
you
written
this
draft?
Okay,
do
try
to
tell
your
readers
what
it's
there
for,
don't
just
say:
oh
here's,
an
idea.
Sometimes
it
can
be
really
hard
to
write
this
down.
But
but
if
you
don't
know
it,
then
nobody
else
will
know
it
so
state
the
problem
you're
solving.
Clearly,
in
a
few
words
with
a
picture.
That's
like
key.
If
you
don't
know
what
problem
you're
solving,
then
what
are
you
doing
if
you're
not
using
and
pre-existing
mechanism
say
so
say
why
you're
not
doing
it?
C
Not
just
I've
got
something
new
and
it
works,
but
I've
got
something
new
and
it
worked,
and
it
solves
this
deficiency
be
aware
that
a
problem
statement
is
not
the
same
as
a
use
case,
often
sometimes,
and
news
places
with
I.
Think
we
see
a
lot
at
the
moment
of
drafts
that
try
to
list
they've
got
a
wonderful
new
idea
for
a
prototype
and
then
I
just
ten
use
cases,
and
maybe
nine
of
them
are
just
thrown
stuff
the
wall
to
see
what
sticks
and
one
of
them
is
the
golden.
C
C
C
C
C
It
should
have
all
that
boilerplate.
It
should
have
placed
markers
for
staff,
but
if
you
write
a
full
spec,
the
first
time
you
posted
it,
it
is
perfect,
then,
probably
nobody's
going
to
review
it
and
discuss
it.
It's
kind
of
interested
in
psychology,
but
you
want
to
hook
the
working
group
into
talking
about
your
your
document,
but
by
the
time
you
go
to
working
group,
the
school
and
certainly
by
the
time,
the
document.
C
But
by
the
time
you
get
to
working
with
law
school,
the
the
document
really
needs
to
be
right.
You
must
think
it's
complete
as
independent
submissions.
Editor
I've
just
picked
up
a
document
that
which
has
got
a
publication
request,
and
it's
got
three
sections
in
it
that
say:
TBD;
okay,
that's
not
ready
for
publication.
A
At
the
time,
so
this
is
the
part
of
the
adrian
I
asked
me
to
help
with,
and
so
I'm
talking
about
the
stream
specific
staff
IETF
stream
is
what
a
lot
of
us
do,
but
it's
not
everything
that
we
do
in
that
stream.
We
publish-
and
this
is
the
only
omission
that
I
know
in
the
material
that
I
have
four
kinds
of
our
essays
of
standards
track.
Tcp,
experimental
and
informational
RFC's
there's
some
guidance
about
where
you
kind
of
want
to
target
that.
A
But
this
is,
you
know,
figuring
out
what
the
right
answer
is,
is
still
a
minor
art
to
take
your
best
shot,
and
you
know
the
area
director
or
even
the
Ihde
may
ask
ask
questions
about
that,
but
as
they
start
out
and
what
looks
like
the
right
place
to
you,
we
usually
publish
dress
produced
by
working
groups.
Abs
can
sponsored
rafts,
but
why
not
from
working
group
in
working
groups
have
a
lot
of
flexibility,
but
publication
requested
sets
off
a
list
of
machinery
next
slide.
Please
the
machinery
looks
like
this.
A
There's
a
formal
state
machine
for
publication.
I've
got
that
there.
The
reason
you
care
is
because
state
transitions
are
going
to
generate
email,
that
you
will
see
as
an
author
or
as
a
shepherd
or
as
working
group.
Chair
and
I
had
those
listed
there.
So
the
ad
looks
at
it
and
says:
here's
what
you
know:
here's
what
I
see
the
expert
reviews
from
the
Directorate
get
set
off
at
at
last
call
time
and
get
set
off
foretell
a
chance.
A
The
last
call
that
you
get
comments
that
you
get
from
the
community
as
a
whole,
become,
as
that
you
get
from
other
area
directors
during
isg
evaluation.
The
state
going
to
approve
this.
Is
you
know
you?
You
may
think
that
your
finish
take
a
deep
breath,
you're
not,
and
then
things
that
are
in
the
RFC
atatürk.
You
watch
her
eat
questions
from
the
editors
resolving
comments,
and
this
this
is
I,
think
I
hope
this
is
valuable
for
people.
A
You
may
see
feedback
from
your
ad
during
ad
evaluation.
You
may
see
feedback
from
the
broader
ITF
community.
During
last
call,
you
may
see
feedback
from
or
with
my
next
one
area
review
teams
during
last
call
and
even
just
before,
a
tell
a
chat
and
from
other
AEDs
during
IHG
evaluation.
Your
best
strategy
is
to
reply
to
emails
with
comments
to
you
know
to
basically
say:
yes,
I,
this
is
what
I
think
you're
telling
me,
and
this
is
what
I
think
the
response
for
that
should
be.
A
You
don't
have
to
make
changes
to
accommodate
every
comment
even
from
an
area
director.
So
please
do
the
right
thing
and
talk
to
your
document
shepherd
about
when
to
submit,
update,
dress,
that's
hard
to
give
general
guidance
for
one
of
the
things
is,
you
know,
should
you
know,
I
got
I
got
review
comments,
should
I
submit
an
updated
draft
and
the
area
director.
Can
you
know
your
area
director
can
look
and
say
well,
actually,
no
one
else
has
Balan
right.
A
This
would
be
a
great
time
to
do
that,
because
none
of
the
area
directors
have
you
know,
I
mean
they're
gonna.
They
need
to
see
the
new
staff
that
you
may
change
us
to.
You
know,
because
that's
more
that's
more
correct
than
the
stuff
that
either
publication
requested
on
recently.
This
is
also
I.
Think
really
important
to
say.
Recent
is
jeez,
have
taken
comments
in
no
objection
positions
as
seriously
as
they
have
taken
comments
in
discuss
positions.
A
That's
a
good
thing,
because
that
means
that
you're
not
getting
discusses
on
things
that
the
area
director
think
matters
but
doesn't
trust
the
authors
or
the
working
group
or
the
other
area
director
to
address
the
comment.
Okay,
we
probably
about
a
year
in
and
after
I
joined
the
isg.
We
really
kind
of
we've
really
kind
of
changed
on
that,
and
it's
been
it's
been
that
way
for
several
years.
Where
you
know
say
we
don't
you
know
we're
not
going
to
I
know
you
could
put
it
in
a
comment
for
a
no
checks
in
position.
A
A
They
may
be,
they
may
be
wrong
and
they
may
not
understand
what's
going
on,
especially
if
they're
in
another
area,
but
they're
really
trying
to
help.
So
please
please
help
them
help
you
next
slide.
Please
discuss
Bell,
it's
not
that
anyone
would
ever
see
one
of
these
at
the
IETF.
Please
a
statement.
A
A
The
current
describes
criteria
and
non
criteria
are
at
this
link
feel
free
to
take
a
look
at
them.
The
common
things
that
I
see
in
discuss
ballast
on
you
know
the
last
three
or
four
is
Jesus.
I
would
say
the
number
one
that
I
do
is
I
can't
understand
what's
going
on
here.
So
please
keep
non-experts
in
mind
when
you
write
the
people
who
implement
this,
the
stuff
that
you're
doing
may
not
be
in
the
working
group
so
making
sure
that
people
who
haven't
been
involved
in
this
protocol,
since
somebody
thought
it
up
can
implement.
A
It
actually
turns
out
to
be
a
really
useful
thing
for
somebody
to
wonder
about
this
one
a
lot.
This
reveals
personal
identifiable
information,
so
keep
BCP
whoever's
that
one
38
in
mind
when
you
write
the
most
recent
surprise
that
people
have
had.
It
was
the
realization,
slowly
and
painfully
at
discuss
Bell
at
time
basically
saying
you
know
you
don't
think
of
IP
addresses
as
personal
identifiable
personal
identifying
information,
but
a
lot
of
IP
addresses
and
ipv6
prefixes
are
only
used
by
one
person.
A
So
when
somebody
does
something
from
that
IP
address
or
even
from
that
prefix
they're
kind
of
telling
you
something
you
know-
and
you
might
you
know,
maybe
you
want.
Maybe
you
want
to
tell
people
something
you
know
in
your
protocol
about
that,
but
don't
let
that
be
a
surprise
to
you.
When
somebody
asks
about
it,
you
know
we
can.
We
can
do
a
lot.
We
can
do
a
lot
more.
A
A
This
can't
this
isn't
safe
on
the
open
Internet
because
of
congestion
or
because
of
security
or
because
of
scaling,
or
you
know,
whatever.
Whatever
reason
something
that
has
happened,
and
it
happened
about
a
year
in
after
I
joined,
the
is
G.
So
2014
was
that
we
started
I'm,
a
transport
guy
right
so
I'm
here
from
the
transport
area
and
I'm
here
to
help
you.
You
guys
really
have
to
laugh
at
some
of
these
statements
because
they're
intended
to
be
curious,
but
to
say
you
know
we
were
we
were
we
were
doing.
A
We
were
doing
a
lot
of
stuff,
I
think
encapsulations
on
UDP,
so
no
congestion
mechanism
there
and
it
was
not.
You
know
some
of
the
some
of
the
things
that
were
being
encapsulated.
It
had
better
congestion,
you
know
control
mechanisms
than
others,
okay,
so
Adrian
and
some
other
folk
David.
Why
I
want
to
call
out
David
black,
and
there
were
some
other
folks
I-
spend
a
lot
of
time,
trying
to
figure
out
how
to
do
this.
A
Well,
we've
ended
up
with
is
saying
that
if
you
are
doing
something
that
is
useful
on
the
open
Internet
but
may
not
be
safe
on
the
open
Internet,
please
explain
to
us
what
the
considerations
are
to
run
it
on
the
open,
Internet
and
then
explain
to
us
which
of
those
considerations.
You
can
not
worry
about
so
much
if
you're
on
a
managed,
closed,
Network
and
we,
you
know
and
I
think
basically
all
of
the
reason
encapsulation
drafts
have
have
done
something
like
that.
A
So,
like
I
said
you
know,
it's
like
tell
us
what
you
know
tell
us
the
truth.
You
know,
but
you
know
think
about
this
stuff
up
front,
and
you
know
you'll
get
a
lot
more,
no
objections,
and
yet
you
know
I
even
been
yes,
I
mean
some
of
the
stuff.
Why
is
this
should
not
a
must?
This
is
very
much
in
the
way.
This
is
very
much
in
the
vein
of
what
Adrian
was
saying
about.
A
If
it's,
if
it's
a
shirt,
then
that
means
somebody
may
not
do
it
and
if
somebody
doesn't
do
it,
what
what
was
supposed
to
happen
and
we
we.
We
asked
that
question
fairly
frequently
and
there's
a
real
range
of
answers
that
we
get
back.
One
is
that
there
are
certain
you
know.
There
is
a
reason
that
you
would
not
do
this
awesome.
A
Please
put
that
in
it.
You
know,
please
put
that
in
you
know
it
shouldn't
less.
If
you
say
there
are
two
or
three
reasons
why
you
would
do
this,
please
give
an
example
and
explain:
what's
supposed
to
happen.
If
it
doesn't,
you
know
if
it
doesn't
happen.
If
you
say
well,
you
know,
there's
these
legacy
implementations
that
don't
do
this
and
we
want
them
to
be
conforming
with
a
standard
you're
like
that's
all
of
them,
so,
like
I
said
just
be
thinking
about
that
up
front
yeah
was
my
last
one.
A
Yeah
also
need
to
describe
what
happens
when
something
happens
that
shouldn't
next
slide.
Please,
the
IRT
F
stream
I'm,
also
in
the
IR
s
G,
so
I
see
these
also
they
publish
RFC's
in
their
own
stream
and
the
process
for
doing
that
is
given
in
that
link,
RTF
specific
requirements
for
content
in
these
drafts.
Please
note
that
you
know
there's
things
like
saying
this:
is
you
know
this
is
the
this?
Is
the
output
of
a
research
group
in
research?
A
If
you
don't
know
much
about
the
RDF
research
groups,
don't
have
to
have
consensus
that
this
is
the
right
thing
to
do.
They
only
have
to
have
consensus
to
that
publishing.
This
is
valuable.
So
what
level
of
consensus
did
the
research
group
have?
That,
like
I,
said
that's
on
the
checklist?
Okay,
so
you
know
be
aware
of
that.
A
If
you're
going
to
be
doing
something
in
the
IOT
of
stream,
the
drafts
are
usually
the
product
of
the
research
group,
I've
written
actually
I've
been
on
that
I've
been
on
the
IR
s
G
for
probably
five
years.
You
know
seven
years
and
I've
written
I
wrote
the
only
one
that
didn't
come
through
a
research
group
that
I've
seen
go
through
the
IRS
G,
so
you
don't
have
to
go
through
a
research
group
depending
on
what
you're
doing
I
was
writing
a
draft
saying
here's
how
to
here's?
A
Here's
what
I
etf
people
should
know
about
the
IRT
F,
so
it
didn't
come
through
a
research
group
and
that
you
know
large,
published
that,
but
this
stuff
will
usually
come
through
a
research
group.
They
are
not
standards
track,
they
are
experimental
or
informational.
There
is
no
last
call
outside
the
research
group
before
publication.
This
is
very
much
in
the
you
know.
Let
it
live
a
hundred
flowers,
bloom
view
of
what
research
groups
do.
A
The
recent
the
IRS
G
provides
review
and
guidance
for
these
finish
drafts
and
it's
explained
in
the
publication
process
of
the
link.
The
is
G
does
what
is
called
a
RFC
57:42
review
for
conflicts
with
IETF
standards
process,
but
there's
not
a
point
of
IOT
F
stream
drafts.
If
you
crack
open,
RC
57:42,
it
basically
says
these
are
the
five
things
that
the
isg
can
say
back
to
the
iot
of
string.
You
know
IRT
of
stream
controller,
and
you
know
one
of
them
is
we
don't
have
any
objection
to
this
one
of
them?
A
You
know
one
of
them
is.
This
is
related
to
work
in
this
working
group,
but
but
that
shouldn't
block
publication
and
then
you
know
then
you're
like
read
down
to
number
five
or
something
like
that
which
is
basically.
This
is
extending
a
ITF
protocol
in
ways
that
should
go
through
the
IETF
process.
So
that's
all.
That's
literally
all
that
you're
supposed
to
get
back
from
the
is
is
G.
If
you're
publishing
the
IOT
of
string,
the
next
slide,
the
IAB
also
publishes
in
its
own
string,
and
this
is
described
in
RFC
4845.
A
These
are
often
produced
by
entities
that
the
IAB
overseas,
like
IB
programs,
I've,
actually
I've
got
a
draft
in
the
in
the
IAB
stack
evolution
program.
That's
supposed
to
go
out
for
community
comment
like
next
week
or
something
published
by
the
RFC
editor,
which
the
IRB
over
has
oversight
responsibility
for
published
by
the
Ayana,
which
is
the
same
thing
workshop
reports,
that's
for
workshops
that
the
IEP
has
done.
I've
actually
go
yeah.
That's
that's
one
of
those
so
and
these
are
not
standard
struck
either
they
are
usually
informational
and
you'll.
A
You
can
publish
in
the
experimental
drafts
there,
that's
not
common,
but
it,
but
it's
possible.
The
process
is
that
you
will
be
working
closely
with
at
least
one
IB
member.
The
whole
IB
will
review
your
work.
The
IB
will
issue
a
ITF
wide
call
for
comments,
but
this
is
not
an
ITF
last
call.
They
are
not
bound
to
seek
consensus
or
resolve
comments.
The
I,
you
know
this
is
one
of
the
beauties
of
the
IEP.
A
Is
the
IEP
can
do
the
right
thing,
even
if
they're
the
only
people
in
the
room
that
think
it's
that
it's
the
right
thing?
That's
why
I
think
that's
why
they
don't
publish
on
the
standards
track,
the
IAB,
the
iesg.
You
can
say
those
guys
are
right
and
they
can
write
a
BCP.
That
says
those
guys
are
right
and
you
should
read
that
and
we're
going
to
act
like
those
guys
are
right
that
you
know.
So.
That's
the
linkage
there.
C
Yeah,
so
the
independent
streams
publishes
our
C's,
but
they
are
not
IETF
RFC
s.
Okay,
be
very
clear.
You
can
come
to
the
independent
stream
and
get
an
RFC,
and
you
can
pretend
to
be
an
intern
I
ATF
RFC,
but
it's
not.
The
process
is
in
4846
and
what's
going
on
we're
publishing
documents
that
are
rooted
in
the
IETF
standards
process
with
following
that
paradigm,
but
we're
only
producing
information
or
experimental
RFC's.
C
C
But
if
there's
some
Internet
related
technologies
that
are
not
on
the
ITF
agenda
and
not
going
to
be
on
the
ITF
agenda,
if
there's
a
discussion
of
options
or
experiences,
if
there's
a
vendor
specific
protocol,
that
needs
to
be
documented
so
that
other
people
can
produce
implementations
interoperate.
If
there's
a
discussion
of
ITF
processes
or
protocols,
then
those
are
all
in
scope,
and
this
last
one
is
quite
important
and
I.
Think
it's
why
the
independent
stream
exists.
C
C
The
editor
sends
stuff
out
to
volunteers,
a
full
review
and
has
an
editorial
board
to
help.
Those
reviews
are
not
mandatory,
they're,
not
part
of
the
consensus
process
but
they're.
They
form
a
discussion,
and
you
might
look
at
this
in
the
same
way
as
a
journal
paper
would
get
reviews
and
you
would
discuss
with
the
journal
editor.
C
C
C
C
Get
to
summarize,
okay
make
your
draft
clear
and
meaningful.
That's
the
most
important
thing
so
write
carefully.
You
want
it
to
move
quickly
and
smoothly
forward.
So
do
all
the
right
things
early
for
the
process
and
and
for
the
cookbook
you
personally
you're.
Writing
the
draft.
You
are
responsible
for
making
that
high
quality,
so
that
means
fix
the
problems.
C
Early
ask
for
help
early,
don't
leave
it
right
up
to
the
editorial
on
stage
saying:
oh
yeah,
they'll
sort
it
out
do
not
rely
on
the
is
GM
your
RFC
editor
to
catch
and
fix
your
problems,
because
that
way
is
a
good
way
to
meet.
Those
problems
persist
to
introduce
new
problems,
to
delay
your
work
and
make
everybody
unhappy
with
you.
E
C
E
A
People
understanding
the
documents
that
we
produce
anybody
want
to
question
it,
but
what
we've
been
doing
for
a
recent
I
well,
recent,
probably
seven
or
eight
years
is
we've
started
doing
technical
presentations,
these
tutorials
on
Sunday
afternoon,
including
a
technical
material
they're,
like
you,
know,
here's
here's,
this
here's
the
deal
about
yang,
so
we've
had
you
know
so.
We've
had
one
of
those
that
right
now
that
is
probably
the
most
common
way
that
we
do
something
like
training
for
our
material
number.
A
One
number
two:
it
is
fine
for
people
to
write
users
guides
and
things
like
that.
You
know
if
it's
useful
to
produce
that
in
a
working
group.
That
would
be
fine
if
it's
not
useful
to
produce
that
in
working
group.
But
you
understand
how
something
works
and
I'm
not
talking
you,
the
person
who's,
trying
to
understand
it.
I'm
talking
about
you,
the
person
who
already
understands
it.
You
know
the
this
is
I'm
writing
a
check
for
you
here.
A
This
is
a
fine
thing
for
the
independent
stream
edit
to
publish
and
say
this
is
this
person's
best
understanding
of
how
this
works
and
what
your
ways
you
should
use?
It
and
what
the
benefits
are
things
like
that
that
should
be
fine,
and
you
know
that
would
be.
That
would
be
a
pretty,
would
be
a
pretty
easy,
57:42
conflict
review,
which
is,
we
would
have
no
objection
and
we
would
actually
be
thrilled
if
somebody
made
the
protocols
easier
to
implement
and
easier
to
deploy
and
easier
to
operate.
I
think.
C
There
are
the
term
of
things:
working
groups
often
produce
applicability
statements.
This
is
how
you
use
this
protocol
of
a
set
of
protocols
to
achieve
a
particular
function
in
the
network,
but
they're
still
dry
as
we
documents
but
they're,
helping
to
explain
the
use
case.
The
other
thing
is
there
is
nothing
to
prevent
an
informational
pointer
reference
to
education
or
material
about
a
protocol
or
a
use
case
that
lives
outside
the
ATF.
A
E
C
Maturity,
so
you
can
let
you
can
simply
let
it
expire
and
forget
about
it
every
six
months,
an
internet
draft
is
technically
dead.
My
advice,
however,
is
to
repost
the
draft
replacing
the
text
with
a
statement
we've
given
up
on
this.
For
these
reasons,
so
that
the
last
thing
that
was
ever
posted
as
a
draft
with
that
name
is
a
tombstone.
A
There's
actually
a
dead
state
in
the
data
tracker
for
a
draft
that
is,
you
know
we
almost
made
it
over
the
wall,
but
it
was
not.
It
was
not
ready
in
time
or
it
was
it
not
as
good
an
idea
as
we
thought
it
was,
and
so,
if
you
tell
if
you
notate,
the
working
group
chair
tells
the
area
director
that
the
area
director
can
mark
it.
That
way,
and-
and
you
know
everybody
everyone
will
know
and
I
think
that's
one
of
your
part
of
your
question
is
how
would
anybody
know.
D
C
A
A
You
know,
and
my
I
got,
that
as
the
area
director
and
my
guidance
back
was
everybody
stops
reading
when
they
get
to
the
Ayana
considerations
they
think
they're
through.
If
you
you
know,
if
you
want
anybody
to
read
this
I
would
move
it
above
about
that.
There's
there's
no
rule
about
that.
But
don't
you
know
that's
kind
of
the
way
the
community
thinks
about
things
and
and
you're
you're
kind
of
fitting
into
the
way
the
community
thinks
about
things
so
that
people
will
understand.
You
know
well
know
what
they're
looking
at
Thanks.
C
So
I'm
getting
the
sense
that
people
are
leaving
a
room,
but
there
are
still
questions.
So
we
ought
to
finish,
but
please
come
and
ask
your
question
to
us
afterwards
and
as
one
other
thing
the
edgy
team
asks.
Could
you
please
fill
in?
The
survey
is
about
the
the
tutorials
so
that
they
can
help
plan,
but
we're
here
all
week
so
close.