IETF Logo Mail Archive

Re: [Gen-art] Genart last call review of draft-ietf-softwire-iftunnel-04

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 17 May 2019 15:00 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73A3F12008C; Fri, 17 May 2019 08:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=W7oCdltz; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Bf/H2dPI
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 jTqgzxNIAMPt; Fri, 17 May 2019 08:00:36 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9024120317; Fri, 17 May 2019 08:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2538; q=dns/txt; s=iport; t=1558105231; x=1559314831; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=wjWkEm1jEt4Hkk1XQvtJf0RSz9dlURO0Ym4ac0hYDBg=; b=W7oCdltzO4Tl9z4c6drrRbCHx/VADhre6ohxzMex5wRHoVJGEqNs/70n WnVKx0Zv2AQPY/aUTKS9iNVx3pjhAqsXe/jbIAD77WSnAGLyeJl23A6l0 EkKMYxA6mDS/TOKYPKmDPNT31KnrzIAxIG4us+caIQ28oAS2XS19ZbKFy 4=;
IronPort-PHdr: 9a23:GmGysR/LqpS2Rv9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVcObGEvwL/PCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ClAAAGzN5c/5tdJa1kHQEBBQEHBQGBUgcBCwGBPVADaVUgBAsohBKDRwOOdYJXlyeBLoEkA1QJAQEBDAEBHw4CAQGEQAIXgh0jNQgOAQMBAQQBAQIBBG0cDIVKAQEBAwESEREMAQE3AQ8CAQgYAgIjAwICAjAUARACBAENBSKDAAGBagMODwECDJ8gAoE1iF9xgS+CeQEBBYUGGIIPAwaBDCgBi1AXgUA/gREnH4JMPoREF4JzMoImjXWaJQkCgguPI4NYG4Idik6FTINhiTuDFpU3AgQCBAUCDgEBBYFRATWBV3AVZQGCQYIPg2+FFIU/coEpjlkBAQ
X-IronPort-AV: E=Sophos;i="5.60,480,1549929600"; d="scan'208";a="559227685"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 May 2019 15:00:30 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x4HF0U3g007221 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 17 May 2019 15:00:30 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 17 May 2019 10:00:29 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 17 May 2019 10:00:29 -0500
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 17 May 2019 10:00:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wjWkEm1jEt4Hkk1XQvtJf0RSz9dlURO0Ym4ac0hYDBg=; b=Bf/H2dPI+C6R50MifZfktVOYYfn70LaEpfGi9a5O2OcDKrLMc0DDAGPzv7yWXwT8gsMt0W21WYb5nQn9QbIqk0g+33n7bWvrlL5At6HwRTNqtcQEZA4bQLi8shHk/he9IgKlGZ3UtijHUpbipgoHIaRlHgUkTOOYQPYnyXLCNd0=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB4046.namprd11.prod.outlook.com (20.179.149.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.16; Fri, 17 May 2019 15:00:27 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::1990:d953:1387:d1a7]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::1990:d953:1387:d1a7%7]) with mapi id 15.20.1900.010; Fri, 17 May 2019 15:00:27 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "softwires@ietf.org" <softwires@ietf.org>, "draft-ietf-softwire-iftunnel.all@ietf.org" <draft-ietf-softwire-iftunnel.all@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-softwire-iftunnel-04
Thread-Index: AQHVA7KOlpSLh0etjEuDaOxBWKImrKZduSOAgBHjgwA=
Date: Fri, 17 May 2019 15:00:27 +0000
Message-ID: <2E565893-D95A-494C-A6A5-49A87FFD5A7A@cisco.com>
References: <155710932616.5380.16080578287406575461@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA6C53A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA6C53A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.19.0.190512
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:8da4:11f7:4e6a:901f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4e064f4d-927f-4130-e406-08d6dad865f9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR11MB4046;
x-ms-traffictypediagnostic: MN2PR11MB4046:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB40461F2EE26BCEE2C59A126EA90B0@MN2PR11MB4046.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0040126723
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(136003)(346002)(396003)(376002)(39860400002)(189003)(199004)(6436002)(53936002)(110136005)(54906003)(86362001)(99286004)(46003)(5660300002)(2501003)(14454004)(478600001)(316002)(6306002)(6512007)(229853002)(58126008)(33656002)(2906002)(66574012)(6486002)(6246003)(8936002)(446003)(81156014)(8676002)(2616005)(305945005)(11346002)(81166006)(36756003)(7736002)(64756008)(66446008)(91956017)(82746002)(76116006)(68736007)(66556008)(66476007)(102836004)(73956011)(4326008)(186003)(66946007)(83716004)(71190400001)(71200400001)(486006)(6116002)(476003)(76176011)(256004)(14444005)(6506007)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4046; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: gkegJ0ae0Yc9rzwfTjqnYRAvVdsy5AKB00EKuBSNvuCi5cxa7oGyngHozzA4bH1CmZJgwsZwA3r0/MyJbr7TwVx2Rleupj19XUvMJXhQ8L0IfLFLfxuGGKUHQ7iffQmbeOM+ISAvx3puUl3YW/Z180bvZZXNIq6BKrAjelahi3uV+3Xxab65DjEASnc+idtK47zMhhhHbwicmuMFMvGJONfrBKgUkiGWsFGw45n58yo/+Msjg9QZeJV33qO1BnSvXIYsMKbcPyDgbpE0TiJPio8lFezwN9ayWD2rJcJMeRb+OzzEJsg8dlX6JmIEY9mSHyzikMAfewKavOOvV26d5UDuNfTqQGV2tmzzum//5EWjaut0Xsck8iN/v2jT5hffnwi1JmS735Jho12BheOJf8gWvSzdd+hAmCuiKXe1+9U=
Content-Type: text/plain; charset="utf-8"
Content-ID: <736834DA0C92524AA213342D38F0E509@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4e064f4d-927f-4130-e406-08d6dad865f9
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 May 2019 15:00:27.6761 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4046
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PKiP3cA2nX2feF1cNoGRIlZTqiw>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-softwire-iftunnel-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2019 15:00:38 -0000

Dale, thank you very much for the detailed review of this I-D.

Med, thank you for the reply (and the -05), see below my INT AD input to some remarks/questions 

-éric

On 06/05/2019, 09:50, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com> wrote:
    > De : Dale Worley via Datatracker [mailto:noreply@ietf.org]
    > Envoyé : lundi 6 mai 2019 04:22
    > 
    >    3.  Security Considerations
    > 
    >    These identies are intended to be
    >    referenced by other YANG modules, and by themselves do not expose any
    >    nodes which are writable, contain read-only state, or RPCs.
    > 
    > Logically, this is correct, but I think it would read better if
    > s/contain read-only state/contain readable state/.
    
    [Med] I will leave the initial wording. 

EVY> I agree with Med on this one
        
    > 
    >    6.2.  Informative References
    > 
    >    [TUNNELTYPE-IANA-REGISTRY]
    >               Internet Assigned Numbers Authority, "tunnelType
    >               Definitions", <https://www.iana.org/assignments/smi-
    >               numbers/smi-numbers.xhtml#smi-numbers-6>.
    > 
    > Given that this document specifies substantial interaction with this
    > registry, this reference should be normative.
    
    [Med] We used to have this one as normative but we received comments asking to move it informative. I will leave this one to the AD. 
 
EVY> I agree with Dale on this one. The IESG statement on normative/informative references states: "Normative references specify documents that must be read to understand or implement the technology in the new RFC, or whose technology must be present for the technology in the new RFC to work" and the specific IANA registry is indeed required. Thank Med for having move it to the normative section.

v2.23.0 | Report a Bug | By Email