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

Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> Mon, 13 February 2017 14:20 UTC

Return-Path: <veerendranatharv@huawei.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 77A9E1295FA; Mon, 13 Feb 2017 06:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ee6TSViCYt8V; Mon, 13 Feb 2017 06:20:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE3CC1295A1; Mon, 13 Feb 2017 06:20:38 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAO02247; Mon, 13 Feb 2017 14:20:37 +0000 (GMT)
Received: from BLREML407-HUB.china.huawei.com (10.20.4.45) by lhreml702-cah.china.huawei.com (10.201.5.99) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 13 Feb 2017 14:20:36 +0000
Received: from BLREML501-MBX.china.huawei.com ([10.20.5.198]) by BLREML407-HUB.china.huawei.com ([10.20.4.45]) with mapi id 14.03.0301.000; Mon, 13 Feb 2017 19:50:29 +0530
From: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.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: AdKC3shnNhYwdbbrRSWzOM8TNO3Pyv//1RUA//7E0wCAAk1YgIAAsE0A//tOBtA=
Date: Mon, 13 Feb 2017 14:20:29 +0000
Message-ID: <73BFDDFFF499304EB26FE5FDEF20F78850870F7F@blreml501-mbx>
References: <73BFDDFFF499304EB26FE5FDEF20F7885086FA74@blreml501-mbx> <3E1CCF0A-41E5-49E9-82FA-BC96F689A69D@cisco.com> <73BFDDFFF499304EB26FE5FDEF20F7885086FE9C@blreml501-mbx> <2DE89697-41FA-4389-9CDE-A91B7ADE37D1@cisco.com> <771e1235-1a60-806d-3497-276d15c98778@gmail.com>
In-Reply-To: <771e1235-1a60-806d-3497-276d15c98778@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.152.243]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58A1C0B5.01CA, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 80d865ced56b9c30ca47bbad10fc9d6f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5RpVD9SixlTOvqPnd4XVt-02O7M>
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: Mon, 13 Feb 2017 14:20:41 -0000

Using ULA for Adj segment/special segment is good option. 
We can generate these addresses automatically and assign for adjacent  neighbors.

Thanks and Regards,
Veerendranath

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
Sent: 11 February 2017 01:33
To: Stefano Previdi (sprevidi) <sprevidi@cisco.com>om>; Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
Cc: draft-ietf-ospf-ospfv3-segment-routing-extensions@tools.ietf.org; ospf@ietf.org; ipv6@ietf.org; draft-ietf-6man-segment-routing-header@ietf.org
Subject: Re: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH

On 10/02/2017 22:31, Stefano Previdi (sprevidi) wrote:
...
> In the IPv6 dataplane a SID being an IPv6 address, it makes the SID a global IPv6 address (even in the case of Adj-SIDs). This of course is orthogonal to the control plane that may or may not advertise such address.

By the way, be careful with the phrase "global IPv6 address". I think you mean "global scope" (which includes ULA), not "globally reachable" (which excludes ULA).

   Brian