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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 February 2017 22:48 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 BC113129607; Thu, 9 Feb 2017 14:48:43 -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 X63eNp0SXIzq; Thu, 9 Feb 2017 14:48:42 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 1A435129604; Thu, 9 Feb 2017 14:48:42 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id 204so1396819pge.2; Thu, 09 Feb 2017 14:48:42 -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=4CBFcp0pwnLFZ0c9Ky85vBmdKnA9CdRhxEkv2KJj2h0=; b=t5EUazeqnFyXXil4djPaIcN3R6xcCF962YUZideksIWbzC4o0c2FpI0im0fQPpc7ax O+UGTF748Tid/W/XnehRkmcq7lL4903GWCC1J5tLqR49aCaPO0rZlRfpK5eSTSl5uEMF Q8XpTnlePYg7uimXH1z2ze5EZpmaZcZhCHTuyE2h/j8G3IcFNE6HNguQnqRzKau8sMb3 oxYjfRowC103Sw0OSruleM8xWc8mZPvSc8JJWmhWq+ijl4FCBsoEEOrZIkt+1nuam4GL BHtn2PiRpQ/qIlKGAddyYlXCGTmZC0vlclJSLWM1xODECYyFFOIrt6wg56gs/F76eD8J pvmg==
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=4CBFcp0pwnLFZ0c9Ky85vBmdKnA9CdRhxEkv2KJj2h0=; b=A6Ba0UTylCpW4WyqYbESJuS7ajmMsLOAQjXkmfBO91ewVNaBdssjC2I+5f9POqqb8Z hFR4GtNcLreU+bwDLuuTKMO/HpOFXqiFmERpTWDcqqy6Swmw1+8tGStXLZT+4IZBUL+V BdGdy7k9Hj00cNTDoQUi8iDqcAbkMosQvSqdaPqPKYXCsyTvMtqh7CeROo9LgggxqyJC gbsVSAGP6RjMANY/kvVdj2BO351WSYemYROfipW66PSoOq7SdiezEL5gpxxoQGCEyew+ PEENdewypOg1m+Z5Nsl6BuRBoxhvyDkz/zKiAPmx/wH5SZ8JBvyHnvaajV75EE7bIJS4 yUTg==
X-Gm-Message-State: AMke39kYkscewRpVXUNZndYqc/g+rzznOR3RZ3WwC7EYWqPk4yRcJm2XI+rRP5jbwbOgtA==
X-Received: by 10.98.218.9 with SMTP id c9mr6273274pfh.99.1486680521655; Thu, 09 Feb 2017 14:48:41 -0800 (PST)
Received: from ?IPv6:2406:e007:7ac3:1:28cc:dc4c:9703:6781? ([2406:e007:7ac3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id c18sm31409012pfj.49.2017.02.09.14.48.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 14:48:41 -0800 (PST)
Subject: Re: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH
To: Mark Smith <markzzzsmith@gmail.com>, Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
References: <73BFDDFFF499304EB26FE5FDEF20F7885086FA74@blreml501-mbx> <CAO42Z2wuibtYx39tJFAKJ=TdcWLe8tCQHz9YSbaeUHFyJSb8rw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6496ee1a-fa7c-8599-947a-663e112a61ae@gmail.com>
Date: Fri, 10 Feb 2017 11:48:45 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2wuibtYx39tJFAKJ=TdcWLe8tCQHz9YSbaeUHFyJSb8rw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KA-Xdz-5DXS2sX_1WvKxBPUcQTs>
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>, 6man WG <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 22:48:44 -0000

Mark,
On 10/02/2017 08:26, Mark Smith wrote:
> On 10 Feb. 2017 03:02, "Veerendranatha Reddy Vallem" <
> veerendranatharv@huawei.com> wrote:
...
>> If Link local address is Link local, how we can use this address in SRH header, 
>> since IPv6 destination address should not be link local address as per
>> IPv6 protocol.
> 
> I'd be curious where you might have got that idea from.
> LL addresses are perfectly fine as destination addresses, including for
> application traffic. They're even preferred over global and ULA addresses
> by default when there is a choice from a set.

Right, but if an SR header is travelling off-link, which I think must often
be the case, it would be doubleplus ungood to include a LL address, which is
meaningless off-link. So probably using a LL address in SRH needs to be
strictly limited.

   Brian

> Many of the advantages of LLs for end-user applications would also apply to
> network applications such as SR.
> 
> "How to use IPv6 Link-Local Addresses in Applications"
> https://tools.ietf.org/html/draft-smith-ipv6-link-locals-apps-00
> 
> Regards,
> Mark.
> 
> 
> 
> If Adj-Sid is global ipv6 address, means we need to consider “global
> ipv6 interface address” of the neighbor on the link?
> 
> 
> 
> Regards,
> 
> Veerendranath
> 
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>