Re: [CCAMP] Request for early IANA Allocation of values for new flag and RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05
Lou Berger <lberger@labn.net> Mon, 25 August 2014 20:02 UTC
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D76991A030F for <ccamp@ietfa.amsl.com>; Mon, 25 Aug 2014 13:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.409
X-Spam-Level: *
X-Spam-Status: No, score=1.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_EQ_BIZ=0.288, HELO_MISMATCH_BIZ=0.443, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793] 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 KFEE1dCGuyr1 for <ccamp@ietfa.amsl.com>; Mon, 25 Aug 2014 13:02:41 -0700 (PDT)
Received: from newdragon.webhostserver.biz (unknown [69.25.137.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76C4B1A031C for <ccamp@ietf.org>; Mon, 25 Aug 2014 13:02:40 -0700 (PDT)
Received: from localhost ([::1]:55981) by newdragon.webhostserver.biz with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <lberger@labn.net>) id 1XM0TF-0000Xr-KP; Tue, 26 Aug 2014 00:02:30 +0400
Message-ID: <53FB96AD.8040709@labn.net>
Date: Mon, 25 Aug 2014 16:03:57 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'OSCAR GONZALEZ DE DIOS' <oscar.gonzalezdedios@telefonica.com>
References: <CFF3F945.5CB65%oscar.gonzalezdedios@telefonica.com> <53CEE315.8070409@labn.net> <0ef901cfa61d$12b296b0$3817c410$@olddog.co.uk> <D000AF53.5DB71%oscar.gonzalezdedios@telefonica.com> <53DBCB6F.8060801@labn.net> <D01A9B8C.5E7C1%oscar.gonzalezdedios@telefonica.com> <049e01cfc091$cb2a1f40$617e5dc0$@olddog.co.uk>
In-Reply-To: <049e01cfc091$cb2a1f40$617e5dc0$@olddog.co.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - newdragon.webhostserver.biz
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Get-Message-Sender-Via: newdragon.webhostserver.biz: authenticated_id: lberger@blabn.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/kXz7Ccx4BkWarjpFhNM1GP03RbI
Cc: 'CCAMP' <ccamp@ietf.org>, ccamp-ads@tools.ietf.org
Subject: Re: [CCAMP] Request for early IANA Allocation of values for new flag and RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Aug 2014 20:02:47 -0000
Adrian has it right. The best way to craft a request for allocation is to show the exact modification you'd like to see in the exiting IANA registry (based on the text version). Lou On 8/25/2014 2:24 PM, Adrian Farrel wrote: > Hi, > > Not sure whether Lou missed this or just didn't work over the weekend :-) > > Anyway, yes, you need to supply a fully functional IANA Considerations section that tells IANA exactly what to do. > > The easiest way to do this is: > - cut and paste the name of the registry > - cut and paste the name of the sub-registry > - cut and paste the table column headers > (use the ASCII version of the registry) > - fill in the details > > A > >> -----Original Message----- >> From: OSCAR GONZALEZ DE DIOS [mailto:oscar.gonzalezdedios@telefonica.com] >> Sent: 20 August 2014 17:45 >> To: Lou Berger >> Cc: adrian@olddog.co.uk; ccamp-ads@tools.ietf.org; 'CCAMP' >> Subject: Re: [CCAMP] Request for early IANA Allocation of values for new flag >> and RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05 >> >> Hi Lou, >> >> I think we have a misunderstanding. You are referring in your mail to >> the Attributes TLV space (where a new entry should add "Allowed on >> LSP_ATTRIBUTES", "Allowed on LSP_REQUIRED_ATTRIBUTES Reference”). We >> are >> referring to the Attribute Flags section of >> https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te- >> parameters.xhtm >> l which compiles the flags of the Attribute Flags TLV. >> >> The fields there are: >> >> Bit No Name Attribute Flags Path Attribute Flags Resv RRO Reference >> >> >> RFC 5420 says (textually): >> >> "Each bit should be tracked with the following qualities: >> >> - Bit number >> - Defining RFC >> - Name of bit >> - Whether there is meaning in the Attribute Flags TLV on a Path >> - Whether there is meaning in the Attribute Flags TLV on a Resv >> - Whether there is meaning in the RRO Attributes subobject >> “ >> >> I guess these are the columns we should include. Right? >> >> Óscar >> >> >> >> >> El 01/08/14 13:16, "Lou Berger" <lberger@labn.net> escribió: >> >>> Oscar, >>> Thanks for the update. I think you missed a couple of things that >>> were in my request to Adrian: >>> >>> 1. For Attributes TLV Space, please provide all columns in the registry, >>> i.e., "Type", "Name", "Allowed on LSP_ATTRIBUTES", "Allowed on >>> LSP_REQUIRED_ATTRIBUTES Reference". >>> >>> 2. Add "value 34 is suggested to align with exclude route" (I mistakenly >>> said ERO in my previous mail) >>> >>> Once these changes are submitted I can forward the early allocation >>> request. >>> >>> Thanks, >>> Lou >>> >>> On 8/1/2014 2:46 AM, OSCAR GONZALEZ DE DIOS wrote: >>>> Hi Adrian, Lou, >>>> >>>> I have posted a new version of the draft >>>> draft-ietf-ccamp-rsvp-te-srlg-collect, in which it is highlighted in the >>>> IANA section the values whose early allocation is requested. >>>> >>>> Should there be any issues with the IANA section, let the authors know >>>> asap. >>>> >>>> Best Regards, >>>> >>>> Óscar >>>> >>>> >>>> >>>> El 22/07/14 22:23, "Adrian Farrel" <adrian@olddog.co.uk> escribió: >>>> >>>>> Hi, >>>>> >>>>> I approve. >>>>> >>>>> Please check that the IANA section of the draft is nice and clean so >>>>> IANA >>>>> can make the right allocations with no ambiguity. >>>>> OR >>>>> Wait a few days for me to have time to check the draft. >>>>> >>>>> Thanks, >>>>> Adrian >>>>> >>>>>> -----Original Message----- >>>>>> From: Lou Berger [mailto:lberger@labn.net] >>>>>> Sent: 22 July 2014 23:18 >>>>>> To: ccamp-ads@tools.ietf.org >>>>>> Cc: CCAMP >>>>>> Subject: Fwd: Request for early IANA Allocation of values for new flag >>>>>> and RRO >>>>>> sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05 >>>>>> >>>>>> >>>>>> Adrian, >>>>>> The WG chairs support the following early allocation request: >>>>>> >>>>>> 1) In the "Attributes TLV Space" section of the "Resource Reservation >>>>>> Protocol-Traffic Engineering (RSVP-TE) Parameters" registry located in >>>>>> https://www.iana.org/assignments/rsvp-te- >>>>>> <https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te- >>>>>> parameters.xhtml> >>>>>> parameters/rsvp-te-parameters.xhtml >>>>>> <https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te- >>>>>> parameters.xhtml>: >>>>>> >>>>>> Type (value to be assigned) >>>>>> Name SRLG Collection Flag >>>>>> Allowed on LSP_ATTRIBUTES yes >>>>>> Allowed on LSP_REQUIRED_ATTRIBUTES yes >>>>>> >>>>>> 2) In the Sub-object type ‒ 21 ROUTE_RECORD portion of the Resource >>>>>> Reservation Protocol (RSVP) Parameters registry located at >>>>>> http://www.iana.org/assignments/rsvp-parameters/rsvp- >> parameters.xhtml: >>>>>> Value: (value to be assigned) 34 is suggested to align with ERO >>>>>> Description: SRLG sub-object >>>>>> >>>>>> 3) In the "Error Codes and Globally-Defined Error Value Sub-Codes, >>>>>> Sub-Codes ‒ 2 Policy Control Failure" section of the "RSVP PARAMETERS" >>>>>> registry located at http://www.iana.org/assignments/rsvp-parameters. >>>>>> Value: (value to be assigned) >>>>>> Description: SRLG sub-object >>>>>> >>>>>> Do you approve this request -- so that we can submit the request (per >>>>>> stpe 5 of RFC7120)? >>>>>> >>>>>> Thank you, >>>>>> Lou (and Deborah) >>>>>> >>>>>> >>>>>> -------- Original Message -------- >>>>>> Subject: Request for early IANA Allocation of values for new flag >>>>>> and >>>>>> RRO sub-object in draft-ietf-ccamp-rsvp-te-srlg-collect-05 >>>>>> Date: Tue, 22 Jul 2014 15:19:35 +0000 >>>>>> From: OSCAR GONZALEZ DE DIOS >>>>>> <oscar.gonzalezdedios@telefonica.com> >>>>>> To: Lou Berger <lberger@labn.net>, DEBORAH A BRUNGARD >>>>>> <db3546@att.com> >>>>>> CC: CCAMP <ccamp@ietf.org> >>>>>> >>>>>> >>>>>> >>>>>> Dear CCAMP WG Chairs, >>>>>> >>>>>> Following the procedure for Early IANA Allocation of Standards Track >>>>>> Code Points defined in Section 3.1 of RFC 7120, on behalf of the >>>>>> authors >>>>>> of the WG draft "RSVP-TE Extensions for Collecting SRLG Information", >>>>>> draft-ietf-ccamp-rsvp-te-srlg-collect-05, it is requested to CCAMP WG >>>>>> chairs the early allocation of the following values: >>>>>> >>>>>> --> Value for a new flag, named "SRLG Collection Flag" in the RSVP >>>>>> Attribute Bit Flags space. IANA has created a registry and manages the >>>>>> space of attributes bit flags of Attribute Flags TLV, as described in >>>>>> section 11.3 of [RFC5420], in the "Attributes TLV Space" section of >>>>>> the >>>>>> "Resource Reservation Protocol-Traffic Engineering (RSVP-TE) >>>>>> Parameters" >>>>>> registry located in >>>>>> https://www.iana.org/assignments/rsvp-te-parameters/rsvp-te- >>>>>> parameters.xhtml. >>>>>> The document "RSVP-TE Extensions for Collecting SRLG >>>>>> Information",draft-ietf-ccamp-rsvp-te-srlg-collect-05, introduces and >>>>>> defines a new Attribute Bit Flag, named "SRLG Collection Flag". It is >>>>>> requested that IANA makes an early assignment of the value of the >>>>>> "SRLG >>>>>> Collection Flag" from the Attribute Bit Flags. >>>>>> >>>>>> --> Type for a new RRO sub-object, named "SRLG sub-object " within the >>>>>> ROUTE_RECORD Object space. IANA has made assignments in the "Class >>>>>> Names, Class Numbers, and Class Types" section of the "RSVP >>>>>> PARAMETERS" >>>>>> registry located at http://www.iana.org/assignments/rsvp-parameters. >>>>>> It >>>>>> is requested that IANA makes an early assignment of the type of the >>>>>> new >>>>>> proposed RRO sub object in the document >>>>>> draft-ietf-ccamp-rsvp-te-srlg-collect-05 named "SRLG sub-object" from >>>>>> the ROUTE_RECORD portions of the mentioned registry. >>>>>> >>>>>> —> Value for a new Policy Control Failure Error sub code. IANA has >>>>>> made >>>>>> assignments in the "Error Codes and Globally-Defined Error Value >>>>>> Sub-Codes" section of the "RSVP >>>>>> PARAMETERS" registry located at >>>>>> http://www.iana.org/assignments/rsvp-parameters. We request that IANA >>>>>> makes an early assignment of a new error sub-code from the Policy >>>>>> Control Failure Sub-Codes registry. >>>>>> >>>>>> The main reason for the request of the early allocation is to >>>>>> facilitate >>>>>> interoperability of early implementations, as other WG documents have >>>>>> also new values in the same registry and clashes have been identified >>>>>> with the suggested values in the draft. >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Oscar >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ----------------------------------------------------------------------- >>>>>> - >>>>>> >>>>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>>>> destinatario, >>>>>> puede contener información privilegiada o confidencial y es para uso >>>>>> exclusivo de la persona o entidad de destino. Si no es usted. el >>>>>> destinatario indicado, queda notificado de que la lectura, >>>>>> utilización, >>>>>> divulgación y/o copia sin autorización puede estar prohibida en virtud >>>>>> de la legislación vigente. Si ha recibido este mensaje por error, le >>>>>> rogamos que nos lo comunique inmediatamente por esta misma vía y >>>>>> proceda >>>>>> a su destrucción. >>>>>> >>>>>> The information contained in this transmission is privileged and >>>>>> confidential information intended only for the use of the individual >>>>>> or >>>>>> entity named above. If the reader of this message is not the intended >>>>>> recipient, you are hereby notified that any dissemination, >>>>>> distribution >>>>>> or copying of this communication is strictly prohibited. If you have >>>>>> received this transmission in error, do not read it. Please >>>>>> immediately >>>>>> reply to the sender that you have received this communication in error >>>>>> and then delete it. >>>>>> >>>>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>>>> destinatário, pode conter informação privilegiada ou confidencial e é >>>>>> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa >>>>>> senhoria o destinatário indicado, fica notificado de que a leitura, >>>>>> utilização, divulgação e/ou cópia sem autorização pode estar proibida >>>>>> em >>>>>> virtude da legislação vigente. Se recebeu esta mensagem por erro, >>>>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>>>> proceda a sua destruição >>>>> _______________________________________________ >>>>> CCAMP mailing list >>>>> CCAMP@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/ccamp >>>> ________________________________ >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener información privilegiada o confidencial y >>>> es para uso exclusivo de la persona o entidad de destino. Si no es >>>> usted. el destinatario indicado, queda notificado de que la lectura, >>>> utilización, divulgación y/o copia sin autorización puede estar >>>> prohibida en virtud de la legislación vigente. Si ha recibido este >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente por >>>> esta misma vía y proceda a su destrucción. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the individual or >>>> entity named above. If the reader of this message is not the intended >>>> recipient, you are hereby notified that any dissemination, distribution >>>> or copying of this communication is strictly prohibited. If you have >>>> received this transmission in error, do not read it. Please immediately >>>> reply to the sender that you have received this communication in error >>>> and then delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinatário, pode conter informação privilegiada ou confidencial e é >>>> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa >>>> senhoria o destinatário indicado, fica notificado de que a leitura, >>>> utilização, divulgação e/ou cópia sem autorização pode estar proibida em >>>> virtude da legislação vigente. Se recebeu esta mensagem por erro, >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>> proceda a sua destruição >> >> ________________________________ >> >> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede >> contener información privilegiada o confidencial y es para uso exclusivo de la >> persona o entidad de destino. Si no es usted. el destinatario indicado, queda >> notificado de que la lectura, utilización, divulgación y/o copia sin autorización >> puede estar prohibida en virtud de la legislación vigente. Si ha recibido este >> mensaje por error, le rogamos que nos lo comunique inmediatamente por esta >> misma vía y proceda a su destrucción. >> >> The information contained in this transmission is privileged and confidential >> information intended only for the use of the individual or entity named above. If >> the reader of this message is not the intended recipient, you are hereby notified >> that any dissemination, distribution or copying of this communication is strictly >> prohibited. If you have received this transmission in error, do not read it. Please >> immediately reply to the sender that you have received this communication in >> error and then delete it. >> >> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, >> pode conter informação privilegiada ou confidencial e é para uso exclusivo da >> pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, >> fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização >> pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem >> por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via >> e proceda a sua destruição >
- [CCAMP] Request for early IANA Allocation of valu… OSCAR GONZALEZ DE DIOS
- [CCAMP] Fwd: Request for early IANA Allocation of… Lou Berger
- Re: [CCAMP] Request for early IANA Allocation of … Adrian Farrel
- Re: [CCAMP] Request for early IANA Allocation of … OSCAR GONZALEZ DE DIOS
- Re: [CCAMP] Request for early IANA Allocation of … Lou Berger
- Re: [CCAMP] Request for early IANA Allocation of … OSCAR GONZALEZ DE DIOS
- Re: [CCAMP] Request for early IANA Allocation of … OSCAR GONZALEZ DE DIOS
- Re: [CCAMP] Request for early IANA Allocation of … Adrian Farrel
- Re: [CCAMP] Fwd: Request for early IANA Allocatio… Adrian Farrel
- Re: [CCAMP] Request for early IANA Allocation of … OSCAR GONZALEZ DE DIOS
- Re: [CCAMP] Request for early IANA Allocation of … Lou Berger
- Re: [CCAMP] Fwd: Request for early IANA Allocatio… OSCAR GONZALEZ DE DIOS
- Re: [CCAMP] Fwd: Request for early IANA Allocatio… Lou Berger
- Re: [CCAMP] Fwd: Request for early IANA Allocatio… OSCAR GONZALEZ DE DIOS
- Re: [CCAMP] Fwd: Request for early IANA Allocatio… Lou Berger