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

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Mon, 13 February 2017 14:34 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 363C612967A; Mon, 13 Feb 2017 06:34:57 -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 eaRXeto8PkTs; Mon, 13 Feb 2017 06:34:55 -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 844831293DC; Mon, 13 Feb 2017 06:34:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1428; q=dns/txt; s=iport; t=1486996495; x=1488206095; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=n9yvQBRj3z8YFijB9ETqbQ6L5MW8jHG7jgMxs8WqFYI=; b=UOXN1yFcYTtZcgDgxEnVD9pQ15qVoVKxdbcTH30HiaeBgPi7BVQEj4P5 caJxlGSieDcUZuSFN3OBh2NHEVu89zQRMoeByVSebxw4opFwvY7BluJQr C0kZsRyp2fG3elSJbH08blbumDjhkzI4DqXDFCaSGFQ0l8/EmBuOkt1JK Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BnAQA6w6FY/5xdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1KBageNWpFtH4gMjSqCDIYiAoJnPxgBAgEBAQEBAQFiKIRpAQE?= =?us-ascii?q?BAwE6PwUHBAIBCBEBAwEBAR4JByERFAMGCAEBBA4FiVIDDQiwT4coDYQQAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHYZMggUIgmKCUYIDgzSCMQEEmzg6AY16hBmRBYo?= =?us-ascii?q?1iF8BHziBAFEVPREBhDMdgWF1AYkggQwBAQE?=
X-IronPort-AV: E=Sophos;i="5.35,156,1484006400"; d="scan'208";a="384917399"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2017 14:34:54 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v1DEYs3u030921 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 13 Feb 2017 14:34:54 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 09:34:53 -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; Mon, 13 Feb 2017 09:34:53 -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: AdKC3shnhVQAsSeqr02qRN73fuHSc///1RUA//7E0wCAA1nwG4AEqxCAgAAEA4A=
Date: Mon, 13 Feb 2017 14:34:53 +0000
Message-ID: <132235FB-7DE0-4D47-8264-A3EE67535474@cisco.com>
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> <73BFDDFFF499304EB26FE5FDEF20F78850870F7F@blreml501-mbx>
In-Reply-To: <73BFDDFFF499304EB26FE5FDEF20F78850870F7F@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.72.243]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <379450503AF58243B203962336CD2C54@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/K2sdB3uITTe17kqYBguzPDPWT9s>
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:34:57 -0000

> On Feb 13, 2017, at 3:20 PM, Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> wrote:
> 
> Using ULA for Adj segment/special segment is good option. 


absolutely, ULA make sense in many use cases are fully supported in the segment routing architecture.


> We can generate these addresses automatically and assign for adjacent  neighbors.

sure. 



s.


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