Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-11.txt>

"Voyer, Daniel" <daniel.voyer@bell.ca> Mon, 16 April 2018 23:24 UTC

Return-Path: <daniel.voyer@bell.ca>
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 0B5BE1271DF for <ipv6@ietfa.amsl.com>; Mon, 16 Apr 2018 16:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 pWJLnjPG0iye for <ipv6@ietfa.amsl.com>; Mon, 16 Apr 2018 16:23:54 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2DC512D779 for <ipv6@ietf.org>; Mon, 16 Apr 2018 16:23:49 -0700 (PDT)
Received: from [85.158.142.192] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-6.bemta.az-b.eu-central-1.aws.symcld.net id BB/0B-25200-38035DA5; Mon, 16 Apr 2018 23:23:47 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFJsWRWlGSWpSXmKPExsVybg1jsm6zwdU og4XrBS22vt/HZvHy7HsmiwPfHRyYPXbOusvusWTJTyaP601X2QOYo1gz85LyKxJYMz5sPMtU 8EKj4uj2D0wNjEs0uhg5OSQE/CT+rnrG1sXIxSEksJ9R4unNy0wQzg1GianbV7BCOKcZJT5eu sfcxcjBwSagIzHnhTxIt4hAqsTp0y3MILawQKhE46d9LBDxMIk37fNYIWw9iX3r3oLFWQRUJZ Y9nQpWzytgJXHuxA12iPlHGSXWHlgKluAUiJVo2/UfrJlRQEzi+6k1TCA2s4C4xK0n85kgzha QWLLnPDOELSrx8vE/sHpRoGW/j71kh4jrSJy9/oQRwjaQ2LoU4jgJAXmJW+/msIH8wiygKbF+ lz7EeHuJJ0c3Qa1SlJjS/ZAd4k5BiZMzn0C1SkocXHEDzBYCqpl3C+QvkPvnA0Pu3HKoe+wlH l7+yjSBUXYWkrNnIaybhWTdLCTrZiFZt4CRdRWjRVJRZnpGSW5iZo6uoYGBrqGhsa6JroWJXm KVbpJeaqlucmpeSVEiUFIvsbxYr7gyNzknRS8vtWQTIzCdMADBDsbj01MOMUpyMCmJ8h6deSV KiC8pP6UyI7E4I76oNCe1+BCjDAeHkgTvMv2rUUKCRanpqRVpmTnAxAaTluDgURLhbQZJ8xYX JOYWZ6ZDpE4x6nI8uTyth1mIJS8/L1VKnHcFSJEASFFGaR7cCFiSvcQoKyXMywh0lBBPQWpRb mYJqvwrRnEORiVh3kCQKTyZeSVwm14BHcEEdMQ14ysgR5QkIqSkGhj1w+91BlhviLhXrlp29d CBiiCOqXedzLw5F92cuUOQxUTv/dww149KvHfCo/6oOh3MWMlT5s6sU/DmlthWr5DUOt2s9pi tJzRvynfcPCT5PP5j/Hw5letpvadVDOYV8D/cpbrh1gIZ06dGDVN3L9m/babSnQSOY7Mn5V2R en4yMZX11IZdE0qVWIozEg21mIuKEwGMssJPrQMAAA==
X-Env-Sender: daniel.voyer@bell.ca
X-Msg-Ref: server-14.tower-237.messagelabs.com!1523921026!671373!1
X-Originating-IP: [206.172.1.99]
X-SYMC-ESS-Client-Auth: outbound-route-from=fail
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2159 invoked from network); 16 Apr 2018 23:23:47 -0000
Received: from tls.exchange.bell.ca (HELO Tls.exchange.bell.ca) (206.172.1.99) by server-14.tower-237.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 16 Apr 2018 23:23:47 -0000
X-CrossPremisesHeadersFilteredBySendConnector: EX13EDGE02-DOR.bell.corp.bce.ca
Received: from DG1MBX01-WYN.bell.corp.bce.ca (198.235.121.231) by EX13EDGE02-DOR.bell.corp.bce.ca (198.235.121.55) with Microsoft SMTP Server id 15.0.1347.2; Mon, 16 Apr 2018 19:23:41 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca (2002:8eb6:120e::8eb6:120e) by DG1MBX01-WYN.bell.corp.bce.ca (2002:8eb6:120b::8eb6:120b) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 16 Apr 2018 19:23:45 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca ([fe80::5dff:3357:ccbc:4e47]) by DG1MBX04-WYN.bell.corp.bce.ca ([fe80::5dff:3357:ccbc:4e47%22]) with mapi id 15.00.1347.000; Mon, 16 Apr 2018 19:23:45 -0400
From: "Voyer, Daniel" <daniel.voyer@bell.ca>
To: Ron Bonica <rbonica@juniper.net>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-11.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-11.txt>
Thread-Index: AQHT1dn2KiYr36zcE0G1Gc3k46yKDw==
Date: Mon, 16 Apr 2018 23:23:45 +0000
Message-ID: <4242C688-8617-4920-8278-53A4E43B9855@bell.ca>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <FB1C6E49-81F7-49DD-8E8B-2C0C4735071B@gmail.com> <SN6PR05MB4240109BD0CEA1C9B10335DEAEB00@SN6PR05MB4240.namprd05.prod.outlook.com>
In-Reply-To: <SN6PR05MB4240109BD0CEA1C9B10335DEAEB00@SN6PR05MB4240.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.24.25.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3737C1F6942274499978C3BEA1EB2A67@exchange.bell.ca>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Received-SPF: SoftFail (EX13EDGE02-DOR.bell.corp.bce.ca: domain of transitioning daniel.voyer@bell.ca discourages use of 198.235.121.231 as permitted sender)
X-OrganizationHeadersPreserved: EX13EDGE02-DOR.bell.corp.bce.ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/v4FiKzfvPpbGHj9Zr2fh-QgkdoA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Apr 2018 23:24:04 -0000

Hi Ron see [DV] inlines


On 2018-04-16, 9:31 AM, "ipv6 on behalf of Ron Bonica" <ipv6-bounces@ietf.org on behalf of rbonica@juniper.net> wrote:

    Folks,
    
    Before the last call ends, I would like to add two more comments:
    
    1) The given that:
    
    - the semantic of a SID is different from the semantic of an IPv6 Address,
    - and that a SID can be copied into the Destination Address Field of IP Header
    - and that the Destination Address Field of an IP Header can carry a SID, even if the packet does not contain an SRH
    
    The document should consider the degree to which it extends the IPv6 Addressing Architecture. This discussion should include both topological instructions and service-based instructions.
[DV] In the context of SRv6, the SID is an IPv6 address.  As known, this IPv6 address is within a prefix owned by an operator or node.  The function of that address is entirely up to the implementation at the destination address.

Once again, it’s totally up to the application developers or operators to determine how they may or may not use the IPv6 addresses they own.  They may implement IP in IP tunneling, or some policy-based routing, or anything else on packets destined to that address.

I don’t see the need to bring other SID types into this draft.  This draft defines an SRH and has done a pretty decent job to date of doing that. It provides two examples of topological instructions.  The definition of other uses for SIDs is an application-based definition and does not fit into a draft defining how to carry and process SIDs in an SRH in general.

    2) In order to reduce the degree to which SRv6 extends the IPv6 Addressing Architecture, the document should represent service-based instructions as Destination Options
[DV] This seems to be another attempt to tell an operator what they may use an IPv6 address for.  You are or course free to put whatever you wish in a destination option and parse its TLVs.  As any other implementation is free to use IPv6 address they own for whatever purpose they choose.    


                                                                        Ron
Dan    
    
    > -----Original Message-----
    > From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Bob Hinden
    > Sent: Thursday, March 29, 2018 4:31 PM
    > To: IPv6 List <ipv6@ietf.org>
    > Cc: Bob Hinden <bob.hinden@gmail.com>
    > Subject: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-
    > 11.txt>
    > 
    > 
    > This message starts a two week 6MAN Working Group Last Call on advancing:
    > 
    >        Title           : IPv6 Segment Routing Header (SRH)
    >        Authors         : Stefano Previdi
    >                          Clarence Filsfils
    >                          John Leddy
    >                          Satoru Matsushima
    >                          Daniel Voyer
    > 	Filename       : draft-ietf-6man-segment-routing-header-11.txt
    > 	Pages          : 34
    > 	Date           : 2018-03-28
    > 
    >      https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header
    > 
    > as a Proposed Standard.  Substantive comments and statements of support
    > for publishing this document should be directed to the mailing list.
    > Editorial suggestions can be sent to the author.  This last call will end on 12
    > April 2018.
    > 
    > An issue tracker will be setup to track issues raised on this document.
    > 
    > Thanks,
    > Bob & Ole
    > 
    > 
    > 
    
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    ipv6@ietf.org
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------