I have now submitted version 04 which I believe addresses the last
call comments. The changes are as follows:
Added the sentence:
The message type is a 4-bit integer with possible values from 0 to 15.
Listing 11-14 as Unassigned.
The references are now all Informational (there was a down
31.01.2011 22:38, Stig Venaas wrote:
I have now submitted version 04 which I believe addresses the last
call comments. The changes are as follows:
Added the sentence:
The message type is a 4-bit integer with possible values from 0 to 15.
Listing 11-14 as Unassigned.
Stig,
Thank you very much
Hi,
On 2011-1-13, at 22:43, Michelle Cotton wrote:
Many believe it makes it very clear to the users of the registry what is
available for assignment. Something we will be rolling out soon (for those
registries with a finite space) will be small charts showing how much of the
registry space
Registered in England Wales No: 1996687
-Original Message-
From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of
Lars Eggert
Sent: 14 January 2011 08:23
To: Michelle Cotton
Cc: Julian Reschke; s...@cisco.com; Adrian Farrel; 'The IETF'
Subject: Re: Last Call on draft-ietf-pim
13.01.2011 18:19, Julian Reschke wrote:
On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
...
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered values)
On 14.01.2011 15:04, Mykyta Yevstifeyev wrote:
13.01.2011 18:19, Julian Reschke wrote:
On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
...
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g.,
Hello all,
Summarizing all LC comments received so far, I'd like to propose the
author of draft-ietf-pim-registry-03.txt the following changes to his
document:
1. Abstract
Explain the abbreviations.
2. Introduction
Explain the abbreviations.
3. Add a new section directly after
On 13.01.2011 03:56, Doug Ewell wrote:
Donald Eastlake wrote:
Almost all registries I'm familiar with explicitly list unassigned
ranges.
The IANA Language Subtag Registry doesn't:
http://www.iana.org/assignments/language-subtag-registry
Obviously it depends on the datatype whether saying
Hello all,
Let me cite RFC 5226, that says:
...
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered values) MUST
provide clear instructions on details of
On 13.01.2011 10:21, Mykyta Yevstifeyev wrote:
Hello all,
Let me cite RFC 5226, that says:
...
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered
13.01.2011 13:31, Julian Reschke wrote:
On 13.01.2011 10:21, Mykyta Yevstifeyev wrote:
Hello all,
Let me cite RFC 5226, that says:
...
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g.,
On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
...
That sounds like an editorial error to me.
any ranges to be *reserved* for Unassigned...
doesn't make any sense at all. They are not reserved.
Yes, that is a type of error, but the meaning is that unassigned and
reserved values MUST
13.01.2011 17:58, Julian Reschke wrote:
On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
...
That sounds like an editorial error to me.
any ranges to be *reserved* for Unassigned...
doesn't make any sense at all. They are not reserved.
Yes, that is a type of error, but the meaning is
On 13.01.2011 17:08, Mykyta Yevstifeyev wrote:
13.01.2011 17:58, Julian Reschke wrote:
On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
...
That sounds like an editorial error to me.
any ranges to be *reserved* for Unassigned...
doesn't make any sense at all. They are not reserved.
Yes,
13.01.2011 18:10, Julian Reschke wrote:
On 13.01.2011 17:08, Mykyta Yevstifeyev wrote:
13.01.2011 17:58, Julian Reschke wrote:
On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
...
That sounds like an editorial error to me.
any ranges to be *reserved* for Unassigned...
doesn't make any
On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
...
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered values) MUST
provide clear instructions on details
Many believe it makes it very clear to the users of the registry what is
available for assignment. Something we will be rolling out soon (for those
registries with a finite space) will be small charts showing how much of the
registry space is unassigned, assigned and reserved (utilizing the
On 13.01.2011 21:43, Michelle Cotton wrote:
Many believe it makes it very clear to the users of the registry what is
available for assignment. Something we will be rolling out soon (for those
registries with a finite space) will be small charts showing how much of the
registry space is
Hi Mykyta,
I am writing to provide some review on the draft-ietf-pim-registry,
that is currently in Last Call,
Many thanks for reviewing.
Furstly, this document does not explain the abreviatures once they has
appeared in the title, abstract and main text.
Good catch. It looks like a number
On 12.01.2011 14:25, Adrian Farrel wrote:
...
Moreover, the initial contents of the regsitry does not mention that
values that are Unassigned.
Yeah, probably worth adding an entry...
11-14 Unassigned
...
My understanding was that if something isn't registered then it's
unassigned. When
On 12.01.2011 15:22, Adrian Farrel wrote:
Entirely at random I clicked on:
http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
http://www.iana.org/assignments/calipso/calipso.xhtml
http://www.iana.org/assignments/lmp-parameters
Looks like IANA tries to fill up all the blanks
On 1/12/2011 5:25 AM, Adrian Farrel wrote:
Hi Mykyta,
I am writing to provide some review on the draft-ietf-pim-registry,
that is currently in Last Call,
Many thanks for reviewing.
Furstly, this document does not explain the abreviatures once they has
appeared in the title, abstract and
Almost all registries I'm familiar with explicitly list unassigned
ranges. In some cases, different unassigned subranges have different
allocation policies. For example, there may be a small unassigned
range of lower values requiring Standards Action with the bulk of the
unassigned values
12.01.2011 22:07, Donald Eastlake wrote:
Almost all registries I'm familiar with explicitly list unassigned
ranges. In some cases, different unassigned subranges have different
allocation policies. For example, there may be a small unassigned
range of lower values requiring Standards Action with
Donald Eastlake wrote:
Almost all registries I'm familiar with explicitly list unassigned
ranges.
The IANA Language Subtag Registry doesn't:
http://www.iana.org/assignments/language-subtag-registry
--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 |
25 matches
Mail list logo
