Re: [CCAMP] [Technical Errata Reported] RFC7260 (4106)

["Adrian Farrel" <[e-mail]>]

Nope, that's OK. I'll handle it.
 
Cheers,
Adrian
 
From: Gregory Mirsky [mailto:[e-mail]] 
Sent: 07 December 2014 13:49
To: [e-mail]
Cc: [e-mail]; [e-mail]; Attila Takacs; [e-mail];
[e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: RE: [Technical Errata Reported] RFC7260 (4106)
 
Hi Adrian,
I agree with the resolution you've proposed.
Please let me know if I need to make changes to the Errata or it can be resolved
based on your proposal.
 
                Regards,
                                Greg
 
From: Adrian Farrel [mailto:[e-mail]] 
Sent: Sunday, December 07, 2014 9:20 PM
To: Gregory Mirsky
Cc: [e-mail]; [e-mail]; Attila Takacs; [e-mail];
[e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: RE: [Technical Errata Reported] RFC7260 (4106)
 
Thanks Greg,
 
I think we could reserve all-1s. But that would need an RFC not an Errata
Report.
The point of the report is to fix the text is accidentally different from what
the authors intended.
 
Cheers,
Adrian
 
From: Gregory Mirsky [mailto:[e-mail]] 
Sent: 07 December 2014 01:22
To: [e-mail]
Cc: [e-mail]; [e-mail]; Attila Takacs; [e-mail];
[e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: RE: [Technical Errata Reported] RFC7260 (4106)
 
Hi Adrian,
thank you for your suggestions. My motivation to make all-1s reserved was to
have symmetry with already reserved all-0s value. If authors of the RFC believe
it is unnecessary then I'm more than happy with the proposed resolution.
 
                Regards,
                                Greg
 
From: Adrian Farrel [mailto:[e-mail]] 
Sent: Friday, December 05, 2014 11:49 PM
To: Gregory Mirsky
Cc: [e-mail]; [e-mail]; Attila Takacs; [e-mail];
[e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: RE: [Technical Errata Reported] RFC7260 (4106)
 
Hi Greg,
 
I'm returning to this after an indecent interval.
 
I checked with IANA and they are OK that we can make this sort of change with an
Errata Report and they are happy.
 
So now we have to agree what it should say.
 
There is an error in your suggested change, I think because in the first table
you show 65533 as IETF review, and in the second as reserved for
experimentation.
 
I am keen to make only the minimal changes to fix the obvious bugs. Therefore I
think there is no need to reserve 65535 and it can remain as an experimental
value.
 
That leaves us with...
 
    IANA has created the "OAM Sub-TLVs" sub-registry of the "RSVP-TE OAM
    Configuration Registry" as follows:
 
    Range       | Note                         | Registration Procedures
    ------------+------------------------------|------------------------
    0-31        | Generic Sub-TLVs             | IETF Review
   32-65533    | Technology-specific Sub-TLVs | IETF Review
    65534-65535 | Experimental Sub-TLVs        | Reserved for
                                               |   Experimental Use
 
    IANA has populated the registry as follows:
 
       Sub-TLV Type | Description                   | Reference
       -------------+-------------------------------+----------
           0        | Reserved                      | [RFC7260]
           1        | OAM Function Flags Sub-TLV    | [RFC7260]
           2-65533  | Unassigned                    |
       65534-65535  | Reserved for Experimental Use | [RFC7260]
 
Is everyone OK with that change?
 
Thanks,
Adrian