Re: [Bgp-autoconf] Short comparison of the different documents.

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 18 March 2020 16:03 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: bgp-autoconf@ietfa.amsl.com
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B862B3A0528 for <bgp-autoconf@ietfa.amsl.com>; Wed, 18 Mar 2020 09:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 pCalqGa1mMlo for <bgp-autoconf@ietfa.amsl.com>; Wed, 18 Mar 2020 09:03:52 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 1E3DA3A073D for <bgp-autoconf@ietf.org>; Wed, 18 Mar 2020 09:03:52 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5B9743789D24F8760123 for <bgp-autoconf@ietf.org>; Wed, 18 Mar 2020 16:03:50 +0000 (GMT)
Received: from dggeme701-chm.china.huawei.com (10.1.199.97) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 18 Mar 2020 16:03:49 +0000
Received: from dggeme704-chm.china.huawei.com (10.1.199.100) by dggeme701-chm.china.huawei.com (10.1.199.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 19 Mar 2020 00:03:47 +0800
Received: from dggeme704-chm.china.huawei.com ([10.9.48.231]) by dggeme704-chm.china.huawei.com ([10.9.48.231]) with mapi id 15.01.1713.004; Thu, 19 Mar 2020 00:03:47 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Randy Bush <randy@psg.com>
CC: Jeffrey Haas <jhaas@pfrc.org>, Warren Kumari <warren@kumari.net>, "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
Thread-Topic: [Bgp-autoconf] Short comparison of the different documents.
Thread-Index: AQHV70I9lASDS4RPqUWxt+vZ2IYdwqg4ffOAgAy5yPD//7izAIAIBZzQ//+dIACAAglgUA==
Date: Wed, 18 Mar 2020 16:03:47 +0000
Message-ID: <2ff128833612405a82c7da66313add2b@huawei.com>
References: <CAHw9_i+0rDUJOR3mAMAh9+whaKX0Koc_VaibbfX1zRzocOAvhw@mail.gmail.com> <20200304220727.GC32422@pfrc.org> <fd21d65cfa0f46b9a02dba4048bc260d@huawei.com> <m2sgidbae5.wl-randy@psg.com> <ee273b6c53494af88708836858a40439@huawei.com> <m2fte77wrh.wl-randy@psg.com>
In-Reply-To: <m2fte77wrh.wl-randy@psg.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.175.23]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/Hwmsn4lZdHU80B9EV0B_AK2Enbo>
Subject: Re: [Bgp-autoconf] Short comparison of the different documents.
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2020 16:03:55 -0000

Hi Randy,

Thanks for your comments and the information about l3dl-ulpc draft. 

In general I agree the value of the attribute should be decided by an operator, and its meaning may be only understood by that operator. While as discussed it may be useful to define a specific attribute type for a set of use cases and describe the typical use cases in some document. The attribute values will not be standardized (at least not all of them).

Best regards,
Jie

> -----Original Message-----
> From: Randy Bush [mailto:randy@psg.com]
> Sent: Wednesday, March 18, 2020 12:49 AM
> To: Dongjie (Jimmy) <jie.dong@huawei.com>
> Cc: Jeffrey Haas <jhaas@pfrc.org>; Warren Kumari <warren@kumari.net>;
> bgp-autoconf@ietf.org
> Subject: Re: [Bgp-autoconf] Short comparison of the different documents.
> 
> jimmy,
> 
> i was perhaps a little subtle.  i contend that the attributes are not decidable
> by anyone other than the op.
> 
> see Attribute List in draft-ymbk-lsvr-l3dl-ulpc
> 
> 3.  Upper Layer Protocol Configuration PDU
> 
>    To communicate parameters required to configure peering and operation
>    of Upper Layer Protocols at IP layer 3 and above, e.g., BGP sessions
>    on a link, a neutral sub-TLV based Upper Layer Protocol PDU is
>    defined as follows:
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |    Type = 9   |                 Payload Length                ~
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    ~               |   ULPC Type   |   AttrCount   |               ~
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    ~       Attribute List ...      |    Sig Type   | Signature Len ~
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    ~               |                 Signature ...                 |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>    The Type and Payload Length are defined in [I-D.ietf-lsvr-l3dl].
> 
>    ULPC Type: An integer denoting the type of the uper layer protocol
> 
>    0     :  Reserved
>    1     :  BGP
>    2-255 :  Reserved
> 
>    The AttrCount is the number of attribute sub-TLVs in the Attribute
>    List.
> 
>    The Attribute List is a, possibly null, set of sub-TLVs describing
>    the configuration attributes of the specific upper layer protocol.
> 
>    An Attribute consists of a one octet Attribute Type, a one octet
>    Attribute Length of the number of octets in the Attribute, and a
>    Payload of arbitrary length up to 253 octets.
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    | Attr Type = 1 |    Attr Len   |            Payload            |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+