Protocol
Only using the word standard when it was determined to be
stable and recommended for wide usage.
Anyway, my 2 cents.
--
Bill McQuillan mcqui...@pobox.com
across page break.
Section 5, para 2:
Implemenations - Implementations
Section 5.1, last para:
String indentifier - String identifier
Section 7, para 1:
Implemenations - Implementations
Section Author's Address:
No email address given for Jukka-Pekka Makela.
--
Bill McQuillan mcqui...@pobox.com
a bunch of running code out there, but
this (and perhaps teasing apart the add and insert concepts into
separate verbs) seems worth the bother.
Barry, as participant
--
Mark Nottingham http://www.mnot.net/
--
Bill McQuillan mcqui...@pobox.com
wondered about that limitation for at least 15 years. I
have come up with possible explanations but without a shred of
evidence from the RFCs.
snip
--
Bill McQuillan mcqui...@pobox.com
of the use of these words in
lowercase that seem NOT be used in a normative way.
If anything I would evaluate the evidence to indicate that the
distinction of case *was intended* to be meaningful.
--
Bill McQuillan mcqui...@pobox.com
on MUST and SHOULD for
only necessary protocol features is sometimes forgotten.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
like if the status is renamed:
Disagree-But-Overruled
the annoyance becomes much smaller.
(Just my 2 cents)
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
in the ID-Announce message.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
, there should probably be
an obvious gap in the number range (going to 5 digit or 6 digit numbers).
-1 (simple sequentially increasing RFC numbers for all items is fine)
-Martin
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf
usage. E.g.:
5^(*FWS , *FWS)10 abc
-
Typo: 2.1 Examples, fourth example should be: ^(-)element
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
reasonable to describe these editing cycles I
am not sure that Full quite captures the goal of this process.
For what it's worth.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
scripts.
Sadly, now we may never know. ;-)
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
.
Not so much 1000 years as 40 years!
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
to be intended to allow for recursive lookup and a proper
NXDOMAIN to be returned as normal. I think that it is specifically intended
NOT be treated specially by resolvers.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https
they should be listed at level Top since they are each
handled by the SLD .arpa rather than the root.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
that the acronym URI is explained (IMHO unnecessarily) but
dtn is not.
Even reading the draft, I could not determine what dtn means.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
text, too?
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
from consideration
without any chance of some engineering judgement (or even horse-trading) to
get the implementations to become interoperable and to resolve the
ambiguity.
OTOH, maybe that WAS the intent of the charter.
--
Bill McQuillan mcqui...@pobox.com
that brought about that change. :-)
Anyway, this tangent has probably run it's course, so I'll drop it on this
list.
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
could be sent *to* a group but not *from* one!
--
Bill McQuillan mcqui...@pobox.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
and some other text changes.
I also hope that some guidelines for standard ways to reference a
particular figure from the ASCII text will be developed.
--
Bill McQuillan [EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org
to the internet as savior!
--
Bill McQuillan [EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
case, should the longitude
always be zero or can it be anything between -180.0 and 180.0?
Section 9.2. Location Privcay
Typo: .Privacy
--
Bill McQuillan [EMAIL PROTECTED]
___
IETF mailing list
IETF@ietf.org
https
update
process.
--
Bill McQuillan [EMAIL PROTECTED]
___
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
of its
local filesystem and its intended usage before using some or all of the
name to store the data.
--
Bill McQuillan [EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
http://www.ietf.org/mailman/listinfo/ietf
the identity of the querier based onwhat?
And how would any one of the targets determine that she was the intended
victim?
--
Bill McQuillan [EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
I am curious why all of the RFC Publication announcements on the
IETF-Announce list since 2007 Jun 20 have been double-spaced throughout,
except for the footer apparently added by the list software.
--
Bill McQuillan [EMAIL PROTECTED]
___
Ietf
than just length, md5 and
charset.
--
Bill McQuillan
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
28 matches
Mail list logo
