Re: [mpls] Early AD comments on draft-ietf-mpls-psc-updates
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 21 March 2014 21:34 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF9B1A0900 for <mpls@ietfa.amsl.com>; Fri, 21 Mar 2014 14:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.553
X-Spam-Level:
X-Spam-Status: No, score=-100.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xctMu-sE4qpP for <mpls@ietfa.amsl.com>; Fri, 21 Mar 2014 14:34:37 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id DFA501A07F8 for <mpls@ietf.org>; Fri, 21 Mar 2014 14:34:36 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s2LLYQab014237; Fri, 21 Mar 2014 21:34:26 GMT
Received: from 950129200 (14.21.90.92.rev.sfr.net [92.90.21.14]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s2LLYNAn014213 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Mar 2014 21:34:25 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eric Osborne' <eric@notcom.com>, 'Loa Andersson' <loa@pi.nu>
References: <290801cf4210$dccee410$966cac30$@olddog.co.uk> <CA+97oKMEpLmkvLSbfDePVM_qszvSENgBOT5awB1++b1ii8sZeg@mail.gmail.com> <055001cf4455$98a3e320$c9eba960$@olddog.co.uk> <CA+97oKMsYrW+iqTVNV+aXjy22VzYZ5YE929M=uYykqvPCnF0Sg@mail.gmail.com> <056101cf4459$257a1690$706e43b0$@olddog.co.uk> <532B1921.5020205@pi.nu> <CA+97oKM6woYXsTOTLMMyMoK0ftxdnr6Rq_5d=bv140sNO+_qtw@mail.gmail.com> <532C2803.5040900@pi.nu> <CA+97oKMcdzSMi4NaCGOYocS4zv2gHQcsH5QK9sDFvjUtnnpzsA@mail.gmail.com>
In-Reply-To: <CA+97oKMcdzSMi4NaCGOYocS4zv2gHQcsH5QK9sDFvjUtnnpzsA@mail.gmail.com>
Date: Fri, 21 Mar 2014 21:34:25 -0000
Message-ID: <098401cf454d$55e4a580$01adf080$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKd4omFfmWRtw0yUVmghp/7/GOE0gKXTydrAm+ayxoCEqd62gFLD9z6AhAaCK8A86ow3wINlz2FAqh8+cKYzeGI0A==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20582.002
X-TM-AS-Result: No--58.569-10.0-31-10
X-imss-scan-details: No--58.569-10.0-31-10
X-TMASE-MatchedRID: Kx0w2sAofbtNlZ1zEcyAY7xygpRxo469nophrTcsI7badW4iYSMjUae7 nmhJA6kzQRaE9eMcoEmW0ymMoJMPNZEYDbcmxNrfUSn3o+eoUmxVftPGBTR0roZ9m2yOY6FF5iZ o5ocOnrqkgYMXP5V9yjeT288mssTUYTmYMPkC1lXAJnGRMfFxyRluk36HDQp7NOnYXKcDRxAot4 eEXmG2l9CQaPiFU4Jx+s+5Hj9SlaakwgC+Vcwnna91/YHX0i1lrMhiXlEWsmoJF2U8dKhm+TPqf jabMGZqCxhyF2E3wFe5SMKXxCE4WdvadCKgTaGc3FqOVb7PDEIsCc2iFTIxrfBnFoUlf6vVmEUX ELy30t8zgFcfUB8P8xZyqzF4mL7rOkjQDRo1OZRIRA38P/dwbh9fNWA7SFWqZLnkmkfv+p10zqV mWYjG/TWiq8flgCo5RuoM50Cj0PUHs5+TOPM3e+qwWVBfMuvoRJK67OhGmkO5fo1ci85guyuf1b PUJhSwF3l8kITIdS/AnZqPNq+/SWFqPXSLpNdAQr2qXCJMSV/x6DjDLao3TjYPr4rywPgwaiNyC dipM5ri8zVgXoAltlwtzewu2M63Z5p7FmahraCx5amWK2anSPoLR4+zsDTtAqYBE3k9Mpw=
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/qM3jtja09934sai8l2kLrIRGz4A
Cc: 'Eric Osborne' <eric.osborne@notcom.com>, mpls@ietf.org
Subject: Re: [mpls] Early AD comments on draft-ietf-mpls-psc-updates
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Mar 2014 21:34:39 -0000
Yes. You can use [This.I-D] or the formulation you have. Please post. Thanks, Adrian > -----Original Message----- > From: Eric Osborne [mailto:eric@notcom.com] > Sent: 21 March 2014 13:40 > To: Loa Andersson > Cc: Adrian Farrel; Eric Osborne; mpls@ietf.org > Subject: Re: [mpls] Early AD comments on draft-ietf-mpls-psc-updates > > OK, so: > > --- > 8. IANA Considerations > > IANA is requested to mark the value 0 in the "MPLS PSC TLV Registry" > as "Reserved, not to be allocated" and to update the references to > show [RFC6378] and [RFC-ietf-mpls-psc-updates-03]. Note that this > action provides documentation of an action already taken by IANA but > not recorded in RFC 6378 > --- > > Adrian? > > > > > eric > > > On Fri, Mar 21, 2014 at 7:52 AM, Loa Andersson <loa@pi.nu> wrote: > > Folks, > > > > I'm OK with that text, however it is a documentation of change to a > > standards track RFC. I'm not sure that it is a good idea to ask the > > RFC Editor to remove the text. > > > > I think the RFC Editor will change it to "IANA has marked the > > value 0 ..." I think this should stay in the document. > > > > /Loa > > > > > > On 2014-03-21 12:44, Eric Osborne wrote: > >> > >> OK. Here's the exact text I've got: > >> > >> > >> -- > >> 8. IANA Considerations > >> > >> IANA is requested to mark the value 0 in the "MPLS PSC TLV Registry" > >> as "Reserved, not to be allocated" and to update the references to > >> show [RFC6378] and [RFC-ietf-mpls-psc-updates-03]. Note that this > >> action provides documentation of an action already taken by IANA but > >> not recorded in RFC 6378. > >> > >> Note to RFC Editor: this section may be removed on publication as an > >> RFC > >> --- > >> > >> > >> I wasn't sure if [This.ID] was intended to provoke variable > >> substitution, nor was I sure whether the square brackets meant that > >> the self-reference should also be a normative reference (to the > >> eventual This.RFC). It seems overkill for a document to cite itself > >> as a normative reference ("in order to understand this document, you > >> should read it")...but on the other hand, perhaps we should start > >> doing that for all drafts that come out of MPLS now. > >> > >> I took the exact formatting from the reference section of the MPLS PSC > >> TLV Registry, which does it like this: > >> > >> --- > >> Reference > >> [RFC6378][RFC-ietf-mpls-moving-iana-registries-04] > >> --- > >> > >> and I did not cite the draft itself in its normative reference section. > >> > >> Please let me know if this exact text is acceptable and then I will > >> post the draft. > >> > >> > >> > >> > >> > >> eric > >> > >> > >> On Thu, Mar 20, 2014 at 12:36 PM, Loa Andersson <loa@pi.nu> wrote: > >>> > >>> Folks, > >>> > >>> I can live with the: > >>> > >>> "...update the references to show [RFC6378], [This ID]". > >>> > >>> It is correct that the action was taken for RFC 6378, but it is > >>> also correct that it was never mentioned in RFC 6378. So I guess > >>> that what we need to say is: > >>> > >>> > >>> "IANA is requested to mark the value 0 in the "MPLS PSC TLV Registry" > >>> as "Reserved, not to be allocated" and to update the references to > >>> show [RFC6378], [This.I-D]. Note that this action provides > >>> > >>> documentation of an action already taken by IANA but not recorded > >>> in RFC 6378. This is an update to RFC 6378." > >>> > >>> /Loa > >>> > >>> > >>> On 2014-03-20 17:26, Adrian Farrel wrote: > >>>> > >>>> > >>>> The action was taken for RFC 6378, so it should be mentioned. > >>>> > >>>>> -----Original Message----- > >>>>> From: Eric Osborne [mailto:eric@notcom.com] > >>>>> Sent: 20 March 2014 16:18 > >>>>> To: Adrian Farrel > >>>>> Cc: Eric Osborne; mpls@ietf.org > >>>>> Subject: Re: Early AD comments on draft-ietf-mpls-psc-updates > >>>>> > >>>>> OK. > >>>>> Loa's suggestion is > >>>>> > >>>>> "... update the reference to RFC 6378 to say [this ID]" > >>>>> > >>>>> Adrian's is "...update the references to show [RFC6378], [This ID]". > >>>>> > >>>>> I think Loa's makes more sense...why would we have the registry > >>>>> allocation point to both 6378 and thisID if 6378 doesn't say anything? > >>>>> > >>>>> Whatever text you guys agree on, I'll use. > >>>>> > >>>>> > >>>>> > >>>>> eric > >>>>> > >>>>> On Thu, Mar 20, 2014 at 12:01 PM, Adrian Farrel <adrian@olddog.co.uk> > >>>>> wrote: > >>>>>> > >>>>>> > >>>>>> Yes, you're right. Should be a comma not a period. > >>>>>> > >>>>>> A > >>>>>> > >>>>>>> -----Original Message----- > >>>>>>> From: Eric Osborne [mailto:eric@notcom.com] > >>>>>>> Sent: 20 March 2014 14:39 > >>>>>>> To: Adrian Farrel > >>>>>>> Cc: Eric Osborne; mpls@ietf.org > >>>>>>> Subject: Re: Early AD comments on draft-ietf-mpls-psc-updates > >>>>>>> > >>>>>>> Hi Adrian- > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Thanks for these. I am OK with them and will add them to the > >>>>>>> version I post next. I'm not clear on the nuances of your IANA text, > >>>>>>> though. You say: > >>>>>>> > >>>>>>> > >>>>>>> --- > >>>>>>> IANA is requested to mark the value 0 in the "MPLS PSC TLV Registry" > >>>>>>> as "Reserved, not to be allocated" and to update the references to > >>>>>>> show [RFC6378]. > >>>>>>> [This.I-D]. Note that this action provides documentation of an > >>>>>>> action > >>>>>>> already taken by IANA but not recorded in RFC 6378. > >>>>>>> --- > >>>>>>> > >>>>>>> > >>>>>>> What exactly does the [This.I-D] do in its own sentence? Did you > >>>>>>> mean > >>>>>>> something like " update the references to show [RFC6378] and > >>>>>>> [This.I-D]. Note that this action..." or is there something subtle > >>>>>>> I'm not picking up on with your original phrasing? > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> eric > >>>>>>> > >>>>>>> On Mon, Mar 17, 2014 at 2:43 PM, Adrian Farrel <adrian@olddog.co.uk> > >>>>> > >>>>> > >>>>> wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>> Hi Eric, > >>>>>>>> > >>>>>>>> A couple of discussion points on draft-ietf-mpls-tp-psc-itu (which > >>>>>>>> is > >>>>>> > >>>>>> > >>>>>> currently > >>>>>>>> > >>>>>>>> > >>>>>>>> in IESG evaluation) have given rise to two small proposed additions > >>>>>>>> to > >>>>>>>> draft-ietf-mpls-psc-updates > >>>>>>>> > >>>>>>>> 1. I think this warrants a very small section of its own... > >>>>>>>> > >>>>>>>> x.y PSC TLV Format > >>>>>>>> > >>>>>>>> [RFC6378] defines the capability to carry TLVs in the PSC messages. > >>>>>>>> This > >>>>>> > >>>>>> > >>>>>> section > >>>>>>>> > >>>>>>>> > >>>>>>>> defines the format to be used by all such TLVs. > >>>>>>>> > >>>>>>>> Type field (T) > >>>>>>>> A two octet field that encodes a type value in network byte order. > >>>>>>>> The > >>>> > >>>> > >>>> type > >>>>>>>> > >>>>>>>> > >>>>>>>> values are recorded in the IANA registry "MPLS PSC TLV Registry". > >>>>>>>> > >>>>>>>> Length field (L) > >>>>>>>> A two octet field that encodes the length in octets of the Value > >>>>>>>> field > >>>>>>>> in > >>>>>>>> network byte order. The value of this field MUST be a multiple of 4. > >>>>>>>> > >>>>>>>> Value field (V) > >>>>>>>> The contents of the TLV. This field MUST be a multiple of 4 octets > >>>>>>>> and > >>>>>>>> so > >>>>>> > >>>>>> > >>>>>> may > >>>>>>>> > >>>>>>>> > >>>>>>>> contain explicit padding. > >>>>>>>> > >>>>>>>> > >>>>>>>> 2. There was a trivial snafu with the 0 value in the "MPLS PSC TLV > >>>>>> > >>>>>> > >>>>>> Registry". It > >>>>>>>> > >>>>>>>> > >>>>>>>> was agreed that 0 would be reserved, but this was not recorded in > >>>>>>>> RFC > >>>> > >>>> > >>>> 6378. > >>>>>>>> > >>>>>>>> > >>>>>>>> Therefore, the IANA section of draft-ietf-mpls-psc-updates should > >>>>>>>> include > >>>>>> > >>>>>> > >>>>>> the > >>>>>>>> > >>>>>>>> > >>>>>>>> text... > >>>>>>>> > >>>>>>>> IANA is requested to mark the value 0 in the "MPLS PSC TLV Registry" > >>>>>>>> as > >>>>>>>> "Reserved, not to be allocated" and to update the references to show > >>>>>>> > >>>>>>> > >>>>>>> [RFC6378]. > >>>>>>>> > >>>>>>>> > >>>>>>>> [This.I-D]. Note that this action provides documentation of an > >>>>>>>> action > >>>>>> > >>>>>> > >>>>>> already > >>>>>>>> > >>>>>>>> > >>>>>>>> taken by IANA but not recorded in RFC 6378. > >>>>>>>> > >>>>>>>> > >>>>>>>> Hope everyone is comfortable with this. > >>>>>>>> > >>>>>>>> Thanks, > >>>>>>>> Adrian > >>>>>>>> > >>>>>> > >>>> > >>>> _______________________________________________ > >>>> mpls mailing list > >>>> mpls@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/mpls > >>>> > >>> > >>> -- > >>> > >>> > >>> Loa Andersson email: loa@mail01.huawei.com > >>> Senior MPLS Expert loa@pi.nu > >>> Huawei Technologies (consultant) phone: +46 739 81 21 64 > > > > > > -- > > > > > > Loa Andersson email: loa@mail01.huawei.com > > Senior MPLS Expert loa@pi.nu > > Huawei Technologies (consultant) phone: +46 739 81 21 64
- [mpls] Early AD comments on draft-ietf-mpls-psc-u… Adrian Farrel
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Huub van Helvoort
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Eric Osborne
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Adrian Farrel
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Eric Osborne
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Adrian Farrel
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Loa Andersson
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Eric Osborne
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Loa Andersson
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Eric Osborne
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Loa Andersson
- Re: [mpls] Early AD comments on draft-ietf-mpls-p… Adrian Farrel