[OSPF] 答复: Benoit Claise's Discuss on draft-ietf-ospf-encapsulation-cap-06: (with DISCUSS and COMMENT)

Xuxiaohu <xuxiaohu@huawei.com> Mon, 11 September 2017 08:20 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC49A13301E; Mon, 11 Sep 2017 01:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 CGyPaN-Jg2EN; Mon, 11 Sep 2017 01:20:37 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A009132F49; Mon, 11 Sep 2017 01:20:35 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DOI41633; Mon, 11 Sep 2017 08:20:33 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 11 Sep 2017 09:20:32 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Mon, 11 Sep 2017 16:20:25 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
CC: "tjw.ietf@gmail.com" <tjw.ietf@gmail.com>, "ospf@ietf.org" <ospf@ietf.org>, "acee@cisco.com" <acee@cisco.com>, "ospf-chairs@ietf.org" <ospf-chairs@ietf.org>, "draft-ietf-ospf-encapsulation-cap@ietf.org" <draft-ietf-ospf-encapsulation-cap@ietf.org>
Thread-Topic: Benoit Claise's Discuss on draft-ietf-ospf-encapsulation-cap-06: (with DISCUSS and COMMENT)
Thread-Index: AQHTIWWrbL117DbmnkiRqGFBQRdS4qKu2TaAgACMXgA=
Date: Mon, 11 Sep 2017 08:20:54 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BC10CC9@NKGEML515-MBX.china.huawei.com>
References: <150407984152.21582.13499330365584334713.idtracker@ietfa.amsl.com> <567c98a4-3105-ccdf-f8e9-4aa082bf7b28@cisco.com>
In-Reply-To: <567c98a4-3105-ccdf-f8e9-4aa082bf7b28@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.184.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0205.59B64752.00EB, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9c1694d0ab152bf526dbbf3016c7aec2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/018Xo55qikJJNykmL5G2k8hmLt0>
Subject: [OSPF] 答复: Benoit Claise's Discuss on draft-ietf-ospf-encapsulation-cap-06: (with DISCUSS and COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 08:20:39 -0000

Hi Benoit,

The Tunnel Encapsulation Capabilities TLV contains one or more Tunnel Encapsulation Type Sub-TLVs which in turn contain Zero or more Tunnel Encapsulation Attribute Sub-TLVs. More specifically, the intent of Tunnel Encapsulation Attribute Sub-TLVs contained in a given Tunnel Encapsulation Type Sub-TLV is to describe the specific parameters to be used for the tunnel indicated by the Type of that Tunnel Encapsulation Type Sub-TLV. 

I wonder whether I have understood your points correctly.

Best regards,
Xiaohu 

> -----邮件原件-----
> 发件人: Benoit Claise [mailto:bclaise@cisco.com]
> 发送时间: 2017年9月11日 15:39
> 收件人: The IESG
> 抄送: tjw.ietf@gmail.com; ospf@ietf.org; acee@cisco.com; ospf-chairs@ietf.org;
> draft-ietf-ospf-encapsulation-cap@ietf.org
> 主题: Re: Benoit Claise's Discuss on draft-ietf-ospf-encapsulation-cap-06: (with
> DISCUSS and COMMENT)
> 
> Dear authors,
> 
> I see that a new version has been posted.
> Can you let me know how my DISCUSS point 2 has been addressed?
> 
> Regards, Benoit
> > Benoit Claise has entered the following ballot position for
> > draft-ietf-ospf-encapsulation-cap-06: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut
> > this introductory paragraph, however.)
> >
> >
> > Please refer to
> > https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-ospf-encapsulation-cap/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > 1. I agree with Tim Wicinski's OPS DIR point about IANA.
> >
> >      The content appears to be fine, but there are some outdated (the
> biggest
> >      one is 5226 replaced by 8126), but its the IANA section which appears
> the
> >      most confusing.
> >
> >      7.1 OSPF Router Information (RI) Registry -  appears fine
> >
> >      7.2 OSPF Tunnel Encapsulation Attribute Sub-TLV Registry
> >
> >      This one defines the values being defined/allocated from "This
> Document"
> >      but in Section 5, each Sub-TLV is defined in other documents, so it's
> >      totally confusing.
> >
> > 2. It's not clear which of the following sub-TLVs are
> > required/relevant/interconnected in the Encapsulation Capability TLV
> >
> >              0    Reserved                                  This
> document
> >              1    Encapsulation                             This
> document
> >              2    Protocol Type                             This
> document
> >              3    Endpoint                                  This
> document
> >              4    Color                                     This
> document
> >              5    Load-Balancing Block                      This
> document
> >              6    IP QoS                                    This
> document
> >              7    UDP Destination Port                      This
> document
> >
> > The only hint is:
> >
> >        Value (variable): Zero or more Tunnel Encapsulation Attribute Sub-
> >        TLVs as defined in Section 5.
> >
> > Zero? really, what's the point?
> > Now, from an operational point of view, which sub-TLVs are required/make
> sense?
> > Are some sub-TLVs irrelevant without others? Ex: Color without
> > Encapsulation Could we have multiple identical sub-TLVs? Ex: Color
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > - Sometimes you use "Encapsulation Capability TLV" (section 3),
> > sometimes "The Tunnel Encapsulation Type Sub-TLV" I guess that: OLD:
> >
> >   The Tunnel Encapsulation Type Sub-TLV is structured 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
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >        |    Tunnel Type (2 Octets)     |        Length (2 Octets)
> |
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >        |
> |
> >        |                            Sub-TLVs
> |
> >        |
> |
> >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > NEW:
> >   The Encapsulation Capability TLV is structured 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
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >        |    Tunnel Type (2 Octets)     |        Length (2 Octets)
> |
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >        |
> |
> >        |                            Sub-TLVs
> |
> >        |
> |
> >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > In section 7.1, should it be?
> > OLD:
> >      Value   TLV Name                                  Reference
> >         -----   ------------------------------------   -------------
> >         TBD1    Tunnel Capabilities                    This document
> >
> > NEW:
> >      Value   TLV Name                                  Reference
> >         -----   ------------------------------------   -------------
> >         TBD1    Encapsulation Capabilities             This document
> >
> > OR:
> >      Value   TLV Name                                  Reference
> >         -----   ------------------------------------   -------------
> >         TBD1    Tunnel Encapsulation Capabilities      This document
> >
> > - Then there is a discrepancy between Sub-TLVs and Value in the
> > related text
> >
> >         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
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >        |    Tunnel Type (2 Octets)     |        Length (2 Octets)
> |
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >        |
> |
> >        |                            Sub-TLVs
> |
> >        |
> |
> >
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > Proposal: Sub-TLVs should be replaced by "Tunnel Encapsulation
> > Attribute Sub-TLVs", and the following text updated:
> >
> >    Value (variable): Zero or more Tunnel Encapsulation Attribute Sub-
> >        TLVs as defined in Section 5.
> >
> > - Then, reading section 5, I see yet another name: "OSPF Tunnel
> > Encapsulation Attribute Sub-TLVs" Section 7.2.
> >
> > You should re-read the document to be consistent with your naming
> > convention, in the text and in the IANA sections.
> >
> >
> > .
> >