Re: The RTGWG WG has placed draft-asechoud-rtgwg-qos-model in state "Candidate for WG Adoption"

tom petch <ietfa@btconnect.com> Sun, 23 June 2019 12:20 UTC

Return-Path: <ietfa@btconnect.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4121912016D; Sun, 23 Jun 2019 05:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 iy_dpWf7LKEL; Sun, 23 Jun 2019 05:20:28 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80133.outbound.protection.outlook.com [40.107.8.133]) (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 3F4F4120072; Sun, 23 Jun 2019 05:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2mVrGR1OlnMG40vSaOrmcfPL2zhm/gFqocRA/zWIrCk=; b=Rznd9/ah5c3Ez/4fd7LUxBWbkRlA5/+13PgGewOT2evz8ob3oxKSzGcg8jaVdn9g6VK8K4nDO7Xf/ip0riXhIIJ9lblwAs3ztsM+SVwn7LnP1a09LpEKtVLa6evuUnfxXogd7xFH9ls/tsG0Yby9gCDDea16CpkbfE1jnQKW6Vg=
Received: from VI1PR07MB5646.eurprd07.prod.outlook.com (20.178.81.26) by VI1PR07MB5439.eurprd07.prod.outlook.com (20.178.15.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2008.9; Sun, 23 Jun 2019 12:20:25 +0000
Received: from VI1PR07MB5646.eurprd07.prod.outlook.com ([fe80::ed4f:a89a:d1e:4aef]) by VI1PR07MB5646.eurprd07.prod.outlook.com ([fe80::ed4f:a89a:d1e:4aef%6]) with mapi id 15.20.2008.007; Sun, 23 Jun 2019 12:20:25 +0000
From: tom petch <ietfa@btconnect.com>
To: "Aseem Choudhary (asechoud)" <asechoud@cisco.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, "draft-asechoud-rtgwg-qos-model@ietf.org" <draft-asechoud-rtgwg-qos-model@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: The RTGWG WG has placed draft-asechoud-rtgwg-qos-model in state "Candidate for WG Adoption"
Thread-Topic: The RTGWG WG has placed draft-asechoud-rtgwg-qos-model in state "Candidate for WG Adoption"
Thread-Index: AQHVKFFZz7te3h1bukmzUk7wUzdaiQ==
Date: Sun, 23 Jun 2019 12:20:25 +0000
Message-ID: <013801d529be$0d2ee5c0$4001a8c0@gateway.2wire.net>
References: <156090606508.6966.11992942280049135991.idtracker@ietfa.amsl.com> <00d401d52851$5eb240e0$4001a8c0@gateway.2wire.net> <e6b0d8b3-b842-4a9e-b502-fefa08f24e64@Spark> <BC7EE5F4-C564-4814-B2F7-D5283FEEDEB7@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LNXP265CA0022.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5e::34) To VI1PR07MB5646.eurprd07.prod.outlook.com (2603:10a6:803:c4::26)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfa@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 08065f0d-4dfa-432f-e98a-08d6f7d52b6f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:VI1PR07MB5439;
x-ms-traffictypediagnostic: VI1PR07MB5439:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <VI1PR07MB5439FEB1201764BA525B1941A2E10@VI1PR07MB5439.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:1227;
x-forefront-prvs: 00770C4423
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(136003)(366004)(346002)(376002)(13464003)(189003)(199004)(6306002)(6512007)(9686003)(2201001)(86362001)(44736005)(6436002)(53936002)(229853002)(6486002)(2906002)(446003)(476003)(25786009)(256004)(14444005)(486006)(6246003)(1556002)(14454004)(4720700003)(71200400001)(14496001)(71190400001)(84392002)(2501003)(44716002)(62236002)(5660300002)(66446008)(64756008)(66556008)(66476007)(66946007)(73956011)(110136005)(478600001)(316002)(66066001)(966005)(81156014)(81166006)(50226002)(8936002)(52116002)(186003)(61296003)(8676002)(305945005)(99286004)(102836004)(68736007)(7736002)(3846002)(76176011)(81816011)(81686011)(26005)(386003)(6116002)(53546011)(6506007)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB5439; H:VI1PR07MB5646.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: v18oso20wx+N9j0+jBx65qubi0zzQsJncWKf+IS4fe9kNaVGgEX+M2QZUx5EXDZfc5LGqG4OMRhsYwvA93AzhG6gzGNEr7/AbchBvdB1qEQ7cGDG8N7savD76hVvYMK14a+FDbc0uyRh5VwToEd+8IgWh27i4fZjby5i/9/lCYUtrlq+yV7d1BoM3wKhUmmdgedjnEfOBsDXtDJgfhduzZOsZKl+FFLyr67sSiuUktWtVFQYPaG0BwQwCUoAUsx9oEIXcfbJVfJLWSrEcno/FNDtwHDJIXflILEKwaBKWhjCnO3jCyjasKjIDiMjP2OOkvMf46vBmFWaud0z5vQDOFirn5WiBHq6y2CeZe5O8jSlbUC4pbNiDgLakZgwJAJjtiWbBi4oXfRk9177gUQh9oaCm9Tzz9oQMpdTy7niZz8=
Content-Type: text/plain; charset="utf-8"
Content-ID: <1E4E743CF8B10F47B15681AC8A98DFCF@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 08065f0d-4dfa-432f-e98a-08d6f7d52b6f
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jun 2019 12:20:25.1521 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ietfa@btconnect.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5439
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/4LMpCaPsWPNSU-dUlKdogydLX5k>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jun 2019 12:20:30 -0000

----- Original Message -----
From: "Aseem Choudhary (asechoud)" <asechoud@cisco.com>
Sent: Friday, June 21, 2019 9:42 PM
> Hi Tom, Jeff,
>
> We will be working on it before IETF105.

That is good.  As I said, what I really would like is reference
statements in the YANG module, but while you are at it, you might
consider

s.1 needs a reference for YANG 1.1 i,e, RFC7950

s.2 is the old boilerplate which lacks RFC8174

RFC8343 needs to be a Normative reference for the I-D

RFC7223 is obsoleted by RFC8343

YANG guidelines says that RFC8340 should be a Informative Reference

When you add the Security boilerplate, you will need some more
references for that, ditto IANA Considerations

Tom Petch


>
> -thanks,
> Aseem
>
> From: Jeff Tantsura <jefftant.ietf@gmail.com>
> Date: Friday, June 21, 2019 at 1:40 PM
> To: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>,
"draft-asechoud-rtgwg-qos-model@ietf.org"
<draft-asechoud-rtgwg-qos-model@ietf.org>, "rtgwg@ietf.org"
<rtgwg@ietf.org>, tom petch <ietfa@btconnect.com>
> Subject: Re: The RTGWG WG has placed draft-asechoud-rtgwg-qos-model in
state "Candidate for WG Adoption"
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: <asechoud@cisco.com>, <mjethanandani@gmail.com>,
<nstrahle@juniper.net>, <exa@dscp.org>, <ing-wher_chen@jabil.com>
> Resent-Date: Friday, June 21, 2019 at 1:39 PM
>
> Tom,
>
> Thanks for your comments!
> Co-authors - please work on these, I’d also expect you to have them
incorporated in the version to be presented at IETF105.
>
> Cheers,
> Jeff
> On Jun 21, 2019, 9:50 AM -0700, tom petch <ietfa@btconnect.com>,
wrote:
>
> The challenge I have in reviewing this I-D is the lack of references
in
> the YANG modules for the objects and actions defined therein. I like
to
> have references since they tell me how much I should expect to
> understand, how familiar I should be with the material.
>
> Here we now have references for the YANG import statements (which is
> good) but we should also have references for many of the YANG
> statements; look for example at
> draft-ietf-pim-igmp-mld-yang-15
> for an I-D with a comprehensive list of references in the YANG module.
>
> It may be that here RFC 2697, RFC 2698, RFC3289 are all I need to know
> but I would like to be told that before I start looking into the YANG.
>
> Tom Petch
>
> ----- Original Message -----
> From: "IETF Secretariat" <ietf-secretariat-reply@ietf.org>
> Sent: Wednesday, June 19, 2019 2:01 AM
>
>
> The RTGWG WG has placed draft-asechoud-rtgwg-qos-model in state
> Candidate for WG Adoption (entered by Jeff Tantsura)
>
> The document is available at
> https://datatracker.ietf.org/doc/draft-asechoud-rtgwg-qos-model/
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>