IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 13 February 2017 19:12 UTC

Return-Path: <brian.e.carpenter@gmail.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 2D075129847; Mon, 13 Feb 2017 11:12:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7E9Vkj9QB-Gd; Mon, 13 Feb 2017 11:12:28 -0800 (PST)
Received: from mail-ot0-x242.google.com (mail-ot0-x242.google.com [IPv6:2607:f8b0:4003:c0f::242]) (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 96B241297F7; Mon, 13 Feb 2017 11:12:28 -0800 (PST)
Received: by mail-ot0-x242.google.com with SMTP id 36so13095673otx.3; Mon, 13 Feb 2017 11:12:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=kRbbIfHCvYbCc2qW9qfeRsbQpajolhRMbSAE7CVlqAk=; b=HtDIkaarim4DNhBSr2xjzGrmHARNSH3ftIvCkwyWLueZ6wfFn7znaRxU4jqX065hnP NcIZjdWfFQKQJ5mrZZVXNX+RbVQqd4A+3fF6J/3qyGuEWFTCjAiyNBO6xZYLEm+oQHvM RQlszyISwKMyGsJ+c1YGnF6QCzKibH86PX783D807RGmtk6fAOKDH2OMLf9rtLDUoovR IUTnlJ76ccqn9Ofnsn6TxSaJHfw3q4YQwnMsjzx6IqPCE90erejGcw9RxNulPtl1/F15 25+NtSC6qlQTa9wlGWfNtPIDLGH4qMvuThW/Vcv1VU/3vXd9+pe+OFZfgF27218Rz141 HSxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=kRbbIfHCvYbCc2qW9qfeRsbQpajolhRMbSAE7CVlqAk=; b=eUO9CDRGZmKasoZrdhUfFFM7nY8B9sSkEKCH3mOKB7diznNeboo/8Z56IIdMPQFYxW 872+nhqvjQQKhFBNI8Z1rWJl4h+i9c14ftcp+yaQY7ARthV8horF1NM8fRUX12sxfXsS gKYDvyC+KrWm6oOniPj6hL8U6uEH9oEtvX5w3pP4vmqzYi5Vfz9bi0b5tK3lEZ1F6hNV SpwjqT8n6ToB5Z7/EWJqapPiAGjZ7OxW6zN9+GzvZvexztf/uqGqY6CMJ90+N/tGx8mq KaN6JNJGZldgFIEwfdj/IKHrDFfPbtXSruxE7R6GwQs+bYWc+iMgPw8rqaV0Oh8Bd3fk bDkg==
X-Gm-Message-State: AMke39na13vITLODSbZ8gbVxEAD5R/rLXxEMds3on1qNlmXR5fxpVN/sEEM53GTb9H8gjg==
X-Received: by 10.98.23.207 with SMTP id 198mr27784041pfx.103.1487013147805; Mon, 13 Feb 2017 11:12:27 -0800 (PST)
Received: from [192.168.178.21] ([118.148.112.135]) by smtp.gmail.com with ESMTPSA id z29sm22532051pgc.7.2017.02.13.11.12.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 11:12:27 -0800 (PST)
Subject: Re: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, Veerendranatha Reddy Vallem <veerendranatharv@huawei.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> <132235FB-7DE0-4D47-8264-A3EE67535474@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <95549fb5-030f-e3fd-0e52-305c962faa24@gmail.com>
Date: Tue, 14 Feb 2017 08:12:24 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <132235FB-7DE0-4D47-8264-A3EE67535474@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/urJQnkBzy9Vz4p2B3hNKxTNMqFQ>
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 19:12:30 -0000

On 14/02/2017 03:34, Stefano Previdi (sprevidi) wrote:
> 
>> 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.

That was my assumption. I'm very sensitive to the terminology trap, however,
since I discovered the hard way that the Python ipaddress module thinks that
ULAs are non-global. This confusion may exist in other programming
environments too. (Also see draft-bchv-rfc6890bis.)

   Brian

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

v2.23.0 | Report a Bug | By Email