Re: draft-dong-6man-enhanced-vpn-vtn-id-01
Joel Halpern Direct <jmh.direct@joelhalpern.com> Fri, 31 July 2020 11:07 UTC
Return-Path: <jmh.direct@joelhalpern.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 41C443A12B2 for <ipv6@ietfa.amsl.com>; Fri, 31 Jul 2020 04:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 tu2u4NUTnwIh for <ipv6@ietfa.amsl.com>; Fri, 31 Jul 2020 04:07:57 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 4AC893A03F4 for <6man@ietf.org>; Fri, 31 Jul 2020 04:07:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4BJ4JF0g2Xz6G981; Fri, 31 Jul 2020 04:07:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1596193677; bh=bagB+h/1cjIffJvQEN+VEv397BWt7MEujTR0cz5GxS8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Hy6ddoG0vLMzaYLvLUiiOfODTVSJImE73oUZAhD66s0P83LrQbiku4AtpI0aMCGO4 hLghICDvrslhoFb5OCKnXmYzKhqOcq77tSw6EeD+i8/pn9zFniXvHnnbm+wbG0Hg/O K1+jaQvAxlPZAhgdnNVpEV5eTo9ciQtS0yH/OdUE=
X-Quarantine-ID: <EtOCLXJp0qB5>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.42.2] (mobile-166-171-59-230.mycingular.net [166.171.59.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4BJ4JD0g7cz6G93C; Fri, 31 Jul 2020 04:07:55 -0700 (PDT)
Subject: Re: draft-dong-6man-enhanced-vpn-vtn-id-01
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "6man@ietf.org" <6man@ietf.org>
References: <DM6PR05MB6348F564EE4A9470553B0A8AAE730@DM6PR05MB6348.namprd05.prod.outlook.com> <d579687dd60141b3902706539292a0c4@huawei.com> <3742736f-14b5-ab76-3e9d-d9ad0395eca2@joelhalpern.com> <f9388ba147e147679ec546922c109b07@huawei.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <c502b7a5-2cf9-78a4-5bf3-262febc7fb22@joelhalpern.com>
Date: Fri, 31 Jul 2020 07:07:54 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <f9388ba147e147679ec546922c109b07@huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nXYpy9sRtaWg_figWxeyLBC_a5A>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Jul 2020 11:07:59 -0000
Looking at the draft, and reading your note, you seem to be asking for a hop-by-hop option header which is to be modify the forwarding selection in some unspecified fashion. This kind of open-ended modification of core 6man IPv6 behavior seems a bad idea. Having a modification to the forwarding behavior that may not be noticed or acted on by all routers in the path seems a recipe for forwarding loops. And it is not at all clear that there is any need for this given MPLS, SRH, CRH. Yours, Joel On 7/31/2020 4:47 AM, Dongjie (Jimmy) wrote: > Hi Joel, > > As explained in my previous mail, the role of DSCP and VTN-ID are different. VTN-ID can be used as a in packet identifier of the VTN, and it can be used in a hierarchical manner with DSCP and other fields for packet forwarding. Thus it is not to extend or replace DSCP. > > Best regards, > Jie > >> -----Original Message----- >> From: Joel M. Halpern [mailto:jmh@joelhalpern.com] >> Sent: Wednesday, July 29, 2020 9:40 PM >> To: Dongjie (Jimmy) <jie.dong@huawei.com>; 6man@ietf.org >> Subject: Re: draft-dong-6man-enhanced-vpn-vtn-id-01 >> >> It is unclear to me whether you are asserting that DSCP is insufficiently >> granular to represent the desired treatment, or whether youa re asking for >> an in-packet identifier that does not affect packet queueing or forwarding? >> >> Yours, >> Joel >> >> On 7/29/2020 3:43 AM, Dongjie (Jimmy) wrote: >>> Hi Ron, >>> >>> Thanks for your review and comment. >>> >>> Your interpretation is in the right direction, while the relationship >>> between VTN-ID and DSCP could be considered as in a hierarchical >>> manner, and each is for different purpose. VTN-ID is used to >>> consistently identify a virtual network with a group of network >>> resources allocated from the network, there is no priority difference >>> between VTNs. DSCP is used to provide class (priority) based traffic >>> differentiation, which can be used within VTN. >>> >>> Hope this helps. >>> >>> Best regards, >>> >>> Jie >>> >>> *From:*ipv6 [mailto:ipv6-bounces@ietf.org] *On Behalf Of *Ron Bonica >>> *Sent:* Wednesday, July 29, 2020 1:45 AM >>> *To:* 6man@ietf.org >>> *Subject:* draft-dong-6man-enhanced-vpn-vtn-id-01 >>> >>> Co-authors, >>> >>> In Section 4.2, you say: >>> >>> "There can be different implementations of reserving local network >>> >>> resources to the VTNs. On each interface, the resources allocated >>> to >>> >>> a particular VTN can be seen as a virtual sub-interface with >>> >>> dedicated bandwidth and other associated resources. In packet >>> >>> forwarding, the IPv6 destination address of the received packet is >>> >>> used to identify the next-hop and the outgoing interface, and the >>> VTN >>> >>> ID is used to further identify the virtual sub-interface which is >>> >>> associated with the VTN on the outgoing interface." >>> >>> I interpret this as meaning: >>> >>> -The IPv6 destination address is solely responsible for identifying >>> the IP next hop >>> >>> -The VTNI, along with the DSCP bits, determine how the packet is >>> forwarded to the next-hop >>> >>> So, I can think of the VTNI as "more DSCP bits". >>> >>> Do I have that right? >>> >>> >> Ron >>> >>> Juniper Business Use Only >>> >>> >>> -------------------------------------------------------------------- >>> IETF IPv6 working group mailing list >>> ipv6@ietf.org >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >>> -------------------------------------------------------------------- >>>
- draft-dong-6man-enhanced-vpn-vtn-id-01 Ron Bonica
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Dongjie (Jimmy)
- Re: draft-dong-6man-enhanced-vpn-vtn-id-01 Joel M. Halpern
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Ron Bonica
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Dongjie (Jimmy)
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Dongjie (Jimmy)
- Re: draft-dong-6man-enhanced-vpn-vtn-id-01 Joel Halpern Direct
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Ron Bonica
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Dongjie (Jimmy)
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Dongjie (Jimmy)
- Re: draft-dong-6man-enhanced-vpn-vtn-id-01 Joel M. Halpern
- RE: draft-dong-6man-enhanced-vpn-vtn-id-01 Dongjie (Jimmy)
- Re: draft-dong-6man-enhanced-vpn-vtn-id-01 Joel M. Halpern
- Re: draft-dong-6man-enhanced-vpn-vtn-id-01 Bob Hinden