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

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 23 July 2014 02:23 UTC

Return-Path: <adrian@olddog.co.uk>
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 C36D31A0114 for <ccamp@ietfa.amsl.com>; Tue, 22 Jul 2014 19:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 TkEa1PEIwG7I for <ccamp@ietfa.amsl.com>; Tue, 22 Jul 2014 19:23:20 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C6DC1A03C1 for <ccamp@ietf.org>; Tue, 22 Jul 2014 19:23:19 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s6N2NH96023597; Wed, 23 Jul 2014 03:23:18 +0100
Received: from 950129200 (dhcp-b3fb.meeting.ietf.org [31.133.179.251]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s6N2NE1C023561 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 23 Jul 2014 03:23:15 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Lou Berger'" <lberger@labn.net>, <ccamp-ads@tools.ietf.org>
References: <CFF3F945.5CB65%oscar.gonzalezdedios@telefonica.com> <53CEE315.8070409@labn.net>
In-Reply-To: <53CEE315.8070409@labn.net>
Date: Wed, 23 Jul 2014 03:23:18 +0100
Message-ID: <0ef901cfa61d$12b296b0$3817c410$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGuhldSRgwq0YlUxxNK7p+Q47TGEAJcGeH3m9xLvVA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-20834.003
X-TM-AS-Result: No--40.964-10.0-31-10
X-imss-scan-details: No--40.964-10.0-31-10
X-TMASE-MatchedRID: IeZYkn8zfFrW/bDrA6VrLbxygpRxo469BGvINcfHqhe0Vg+MnSE2GH/2 0wqGUabSTWLw2jvbfpxS13xU66XgGt3j88HhodGN8OsWh3diggqx2AbjyiiRkMi9AjK6C8p1QeJ z9upwOByOiDDBL0DXe3rXRet6mu9irsq/7BhdGyDnjuQQVkVPTfioIsi7Sa0gsneuamRRT5Ml3W kwfnyDsU8mmlqvTMl9vodvpEYj9V4LK4dUlqy0pEYrj4yCOHaSWwKGivsEuI3EXelUnE6spSksj JeAae2uCDrptHUc/xOqG3a/jBZfhjj4RKrox6Ifug9L9GJz8MtF0vHVf0FWQCy6DFF5hapmtTDL ZLR3mBF5OyeMA/FqQex44vPKs+3eaWbbDm4LdIY00dkxYNMRt8yZqgcnwGktztSbQ50f5j4DczT 7r04VrT9GV1ZAneJEY89xjdcdOy57gDs90fC07N7WbjzlfTkve77gz7lToJuAcW0+Rk61r6nyL1 DZazgUgclMfTdtajvXF9jrp/6/uJTVbblBCXFjTuRpUOBlLe/y1N5yYpkPtVADxsP3Lo16iKJu3 ChLBBCpX66kRu+SXUI4W1swQ9AKSJpKBK5xAUnD+IQCVJ3iRm+7CRuDmTtVqo60IlPYBztWPzlt MP6/jdqq7U/PGpXMOqJadNG5QTZAW3ODyfm3/rMjW/sniEQKY9JlLwL1dg3KY//WmIj/oYu3tdA XbWvtcrX2yaJcE9k6W25e1Bs1RC5Am3YGl5jJxDtI40oHM26lY+G3TvhajQAdFMC0xN/9PEIQ6i syHHwcIfeRBwa7IXGaAlsiH8ZWQD5Pc//uvXaeAiCmPx4NwFkMvWAuahr8wxWsZgByNxbe3/9uS SiAvgtuKBGekqUpPjKoPgsq7cA=
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/n3FE-Mcab2Arq-QMc6y9OfLxEI0
Cc: 'CCAMP' <ccamp@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
Reply-To: adrian@olddog.co.uk
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: Wed, 23 Jul 2014 02:23:22 -0000

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>et>, 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