Re: [mpls] [IANA #812064] Protocol Action: 'IANA registries for LSP ping Code Points' to Proposed Standard (draft-ietf-mpls-lsp-ping-registry-03.txt)

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Wed, 18 March 2015 00:44 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: expand-draft-ietf-mpls-lsp-ping-registry.all@virtual.ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 21CE11A6FF2; Tue, 17 Mar 2015 17:44:54 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mpls-lsp-ping-registry.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mpls-lsp-ping-registry.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D411A1BB1 for <xfilter-draft-ietf-mpls-lsp-ping-registry.all@ietfa.amsl.com>; Tue, 17 Mar 2015 17:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.5
X-Spam-Level:
X-Spam-Status: No, score=-9.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, USER_IN_DEF_DKIM_WL=-7.5] 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 PQREbx6lOZSP for <xfilter-draft-ietf-mpls-lsp-ping-registry.all@ietfa.amsl.com>; Tue, 17 Mar 2015 17:44:52 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 053901A6FEF for <draft-ietf-mpls-lsp-ping-registry.all@ietf.org>; Tue, 17 Mar 2015 17:44:52 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com ([173.37.86.79]:64209) by zinfandel.tools.ietf.org with esmtps (TLS1.0:RSA_ARCFOUR_128_SHA1:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <cpignata@cisco.com>) id 1YY26M-0000aI-KX for draft-ietf-mpls-lsp-ping-registry.all@tools.ietf.org; Tue, 17 Mar 2015 17:44:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2788; q=dns/txt; s=iport; t=1426639490; x=1427849090; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=90ZWTxvKrcokLRvlkjlQDZocYTPpIE1NgKvmASkcf64=; b=dksm3syTrDadU0fCS1b2xYb/qQi5q6d6FYa8hOcsq67I4j0KW24yWhzX enlfrboltcPV7OGHVnrJQSRqgCR41ntiLgs5eRG3YfvAMyVK4K+fyjuYS 6rjj1AOBQEmS51dIBmTNEAGoUFtiP+6oxcL0k25FxmCDejdDSmvPTpoaR c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AcBgCqaeJU/49dJa1bgwZSWgTAEoIqhXECgRhDAQEBAQEBfIQNAQEEeRACAQg7CzIlAgQOBQmIJA3OKAEBAQEBAQEDAQEBAQEBAQEaiwyBPYMwB4QqBY1MgWyJN4EYgw2IIUaCQ4M+IoIPI4E8b4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,418,1422921600"; d="scan'208";a="404268673"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-8.cisco.com with ESMTP; 18 Mar 2015 00:44:19 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t2I0huci002966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Mar 2015 00:43:56 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.127]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Tue, 17 Mar 2015 19:43:56 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "drafts-approval@iana.org" <drafts-approval@iana.org>
Thread-Topic: [IANA #812064] Protocol Action: 'IANA registries for LSP ping Code Points' to Proposed Standard (draft-ietf-mpls-lsp-ping-registry-03.txt)
Thread-Index: AQHQYQpeap+AdLyUE0uprHeKN0sfmp0hd+iA
Date: Wed, 18 Mar 2015 00:43:55 +0000
Message-ID: <D12E4203.FE45%cpignata@cisco.com>
References: <RT-Ticket-812064@icann.org> <20150309171626.27954.21671.idtracker@ietfa.amsl.com> <rt-4.2.9-4719-1426634979-1707.812064-7-0@icann.org>
In-Reply-To: <rt-4.2.9-4719-1426634979-1707.812064-7-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [10.82.250.189]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2F54515D0BF2E44D8347D6A02619972E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 173.37.86.79
X-SA-Exim-Rcpt-To: draft-ietf-mpls-lsp-ping-registry.all@tools.ietf.org
X-SA-Exim-Mail-From: cpignata@cisco.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Resent-To: draft-ietf-mpls-lsp-ping-registry.all@ietf.org
Resent-Message-Id: <20150318004452.053901A6FEF@ietfa.amsl.com>
Resent-Date: Tue, 17 Mar 2015 17:44:52 -0700
Resent-From: cpignata@cisco.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-mpls-lsp-ping-registry.all@tools/JUZee8GiziFwsDVtG3NE2Ns1Amc>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/4RUxIymAG1H6zepaoOs4hHfRm6w>
X-Mailman-Approved-At: Wed, 18 Mar 2015 04:25:07 -0700
Cc: "draft-ietf-mpls-lsp-ping-registry.all@tools.ietf.org" <draft-ietf-mpls-lsp-ping-registry.all@tools.ietf.org>
Subject: Re: [mpls] [IANA #812064] Protocol Action: 'IANA registries for LSP ping Code Points' to Proposed Standard (draft-ietf-mpls-lsp-ping-registry-03.txt)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Wed, 18 Mar 2015 00:44:54 -0000

Amanda,

This all looks great to me.

Thanks!

‹ Carlos.

On 3/17/15, 7:29 PM, "Amanda Baber via RT" <drafts-approval@iana.org>
wrote:

>Dear Authors:
>
>ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
>
>We've completed the IANA Actions for the following RFC-to-be:
>
>draft-ietf-mpls-lsp-ping-registry-03
>
>IANA has created the following registries under the "Multi-Protocol Label
>Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" heading:
>
>DS Flags
>Registration Procedure(s): Standards Action
>Reference: [RFC-ietf-mpls-lsp-ping-registry-03]
>
>Bit number 	Name 	Reference
>7	N: Treat as a Non-IP Packet	[RFC4379]
>6	I: Interface and Label Stack Object Request	[RFC4379]
>5-0	Unassigned	
>
>
>Multipath Type
>Registration Procedure(s): Standards Action
>Reference: [RFC-ietf-mpls-lsp-ping-registry-03]
>
>Value 	Meaning 	Reference
>0	no multipath	[RFC4379]
>1	Unassigned	
>2	IP address	 [RFC4379]
>3	Unassigned	
>4	IP address range	[RFC4379]
>5-7	Unassigned	
>8	Bit-masked IP address set	 [RFC4379]
>9	Bit-masked label set 	[RFC4379]
>10-250	Unassigned	
>251-254	Reserved for Experimental Use	[RFC-ietf-mpls-lsp-ping-registry-03]
>255	Reserved	[RFC-ietf-mpls-lsp-ping-registry-03]
>
>
>Pad Type
>Registration Procedure(s): Standards Action
>Reference: [RFC-ietf-mpls-lsp-ping-registry-03]
>
>Value 	Meaning 	Reference
>0	Reserved	[RFC-ietf-mpls-lsp-ping-registry-03]
>1	Drop Pad TLV from reply	[RFC4379]
>2	Copy Pad TLV to reply	[RFC4379]
>3-250	Unassigned	
>251-254	Reserved for Experimental Use	[RFC-ietf-mpls-lsp-ping-registry-03]
>255	Reserved	[RFC-ietf-mpls-lsp-ping-registry-03]
>
>
>Interface and Label Stack Type
>Registration Procedure(s): Standards Action
>Reference: [RFC-ietf-mpls-lsp-ping-registry-03]
>
>Value 	Meaning 	Reference
>0	Reserved	[RFC-ietf-mpls-lsp-ping-registry-03]
>1	IPv4 Numbered	[RFC4379]
>2	IPv4 Unnumbered	[RFC4379]
>3	IPv6 Numbered	[RFC4379]
>4	IPv6 Unnumbered	[RFC4379]
>5-250	Unassigned	
>251-254	Reserved for Experimental Use	[RFC-ietf-mpls-lsp-ping-registry-03]
>255	Reserved	[RFC-ietf-mpls-lsp-ping-registry-03]
>
>
>Please see
>http://www.iana.org/assignments/mpls-lsp-ping-parameters
>
>
>The updated list of Protocol Registries is available here:
> 
>http://www.iana.org/protocols/
>
>Please let us know whether the above IANA Actions look OK. As soon as we
>receive your confirmation, we'll notify the RFC Editor that this
>document's IANA Actions are complete. (If this document has a team of
>authors, one reply on behalf of everyone will suffice.)
>
>We'll update the reference when the RFC Editor notifies us that they've
>assigned a number.
>
>Thanks,
>
>Amanda Baber
>IANA Request Specialist
>ICANN
>