Re: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Thu, 09 February 2017 17:10 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1916E129BFD; Thu, 9 Feb 2017 09:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 pI320_hCI6fH; Thu, 9 Feb 2017 09:10:36 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9416129BAB; Thu, 9 Feb 2017 09:10:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=850; q=dns/txt; s=iport; t=1486660235; x=1487869835; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SQiJnKkBFdFWDPcL4PCEZGWeMR2BNMbJnpex2OLI2tQ=; b=GU7GRx+u5XlIpiyaUXS4Bnpf+z6OmJTHv5OP4e9Ep48Ba76qHD4YOt5U ZQQBc2ATfVZMx0LxEqpbRTtwbVijXa4jtcXYCFdLSFVG1QOpcqfSAc0lJ czYi85zjh7QFDaeKYMiHmOwd+XayrN2Nu+r8B3h0C544zhq7JyTc4dHSB c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A5AQBTopxY/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1GBageDUooIkgmVNoIMhiICGoJRPxgBAgEBAQEBAQFiKIRpAQE?= =?us-ascii?q?BAwEjEUUFCwIBCBgCAiYCAgIwFRACBA4FiWwIsBSCJYtSAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBHYELhUGCBYJqhFSDBi6CMQEEm3ABigyIBYFjGI8KiCyKZgEfODp?= =?us-ascii?q?ETxU8EQGEMh2BYXWHcoEMAQEB?=
X-IronPort-AV: E=Sophos;i="5.35,137,1484006400"; d="scan'208";a="383534280"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Feb 2017 17:10:35 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v19HAYtN003822 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 9 Feb 2017 17:10:35 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 9 Feb 2017 12:10:34 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Thu, 9 Feb 2017 12:10:34 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
Subject: Re: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH
Thread-Topic: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH
Thread-Index: AQHSgvdsLFwCtJj2E0+kqcAvu9rFqw==
Date: Thu, 9 Feb 2017 17:10:34 +0000
Message-ID: <3E1CCF0A-41E5-49E9-82FA-BC96F689A69D@cisco.com>
References: <73BFDDFFF499304EB26FE5FDEF20F7885086FA74@blreml501-mbx>
In-Reply-To: <73BFDDFFF499304EB26FE5FDEF20F7885086FA74@blreml501-mbx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.71.122]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6B6334D37F51A94682FE16082AC73E0E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/b1TFndOGaF58z0v_uki-aj7bCBc>
Cc: "draft-ietf-ospf-ospfv3-segment-routing-extensions@tools.ietf.org" <draft-ietf-ospf-ospfv3-segment-routing-extensions@tools.ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@ietf.org" <draft-ietf-6man-segment-routing-header@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:10:37 -0000

Hi,

the first version of the draft (draft-previdi-6man-segment-routing-header) had a description of Node-SID and Adj-SID. Later, in order to simplify the document, we removed the descriptions and focused the document into the SRH format.

I think it will be helpful to re-introduce a section on the two main SID types (Node, Adjacency). I’m working on an update for the next version.

Thanks.
s.





> On Feb 9, 2017, at 5:02 PM, Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> wrote:
> 
> Dear Authors,
> 
> I am requesting your clarification regarding usage of Adj-SID in SRH header