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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 10 February 2017 20:02 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 033F4129B60; Fri, 10 Feb 2017 12:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 kCJ9Dye34cM8; Fri, 10 Feb 2017 12:02:55 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (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 D9BC4129AFD; Fri, 10 Feb 2017 12:02:47 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id 204so13082377pge.0; Fri, 10 Feb 2017 12:02:47 -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=ecHdBxja+Mqio4kNNnIZxPOxk4GP6tKHulRirBkXG6o=; b=akJo4DXBUy1s6akGvzoEoaw0fSF7dZwwqwbPZs56EAtkqWrgS0n8PFW5LGeQ9OE5lt zRj/vk4nKB6l6IMkHd/fqz1p73W+nc5DIJgrxLZnlJpX2YbkzmQdKvakyP+GFy5hE1uf Lw9Hiba2COyAhO7m9rw3s1r0VGlL+ERYUqmMY6GWzLyoylSEnxPrwC8ViN/4Btxxow5R C/jsS8UVWWR4oSDTdKuY3z/ZBG2WlEsuwsoaQJFrp37x3tICBJIQ9eVv4fstRo5eHT48 Ma96pgmG+YcoCEybKVjsvHQFDmKxfa8ZgJuYxtVvOxB4YfaC7bFmSDKHfLoMvs6QdUkQ 1PNw==
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=ecHdBxja+Mqio4kNNnIZxPOxk4GP6tKHulRirBkXG6o=; b=XvvnRaEb9dSYt2UvefRKpHxjprbr7xmrvvGVKEu1CWlcVHmhda490H8yATLr+HSWUn SC2hsWYAUlvPlcmj49WQgVN1qiTJ0GeKx642uqr1x3Im9703wSfIxq3Dbl4lBImO+iZO hvkUWMUkDIe3mzUwI2CHpIvSTG8lJD44zxFr/V5H+p3ywjIg6K2lIXJQKp9I+cMv5hTK OK87Ios0kQrs3SVKBYxPmB0Fxy2V9R7mAuMQeLh5koy9UL74FKuonv7E9KXLMr6Uz7ZQ Ni3Qy+2cHwMd+xV28IS0JvnW3MD6dAk9KpFOcA2G8QuoUOeyBkv9N7CSUGgQ/BhriMiE caMQ==
X-Gm-Message-State: AMke39mLySedvDbxvdriVXbuR9ZTlWRUAOMA2sx9MTpQUpShzy47yIYHlBLEjKL75siHlg==
X-Received: by 10.84.192.107 with SMTP id b98mr13706743pld.160.1486756967427; Fri, 10 Feb 2017 12:02:47 -0800 (PST)
Received: from ?IPv6:2406:e007:769c:1:28cc:dc4c:9703:6781? ([2406:e007:769c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k76sm7217308pfg.42.2017.02.10.12.02.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 12:02:46 -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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <771e1235-1a60-806d-3497-276d15c98778@gmail.com>
Date: Sat, 11 Feb 2017 09:02:52 +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: <2DE89697-41FA-4389-9CDE-A91B7ADE37D1@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LKlwDGdKZnEFkTrqJv0q2qIRLU4>
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: Fri, 10 Feb 2017 20:02:57 -0000

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