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

"Aseem Choudhary (asechoud)" <asechoud@cisco.com> Fri, 21 June 2019 20:42 UTC

Return-Path: <asechoud@cisco.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 612FD1203C6; Fri, 21 Jun 2019 13:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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=bYYntlAB; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=A4da/Ct5
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 WX_z8EWOXn5M; Fri, 21 Jun 2019 13:42:17 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E3CE1203B2; Fri, 21 Jun 2019 13:42:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11003; q=dns/txt; s=iport; t=1561149737; x=1562359337; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=lr4rlGV1CcVyQo7Z+NRJWZTrTJBYw2P5Eytoiu9IYPA=; b=bYYntlABq21H6ZGy4QeGRMHloVITQrOpOCmzLo1CFunpQ8yVuOqbkPv/ wzRAy9yzEdq0kfzU9ei3ZztBagnUeeV0agTGh83FNc6S17g9Qo5NIPoQm U1eFQ/IdlxjvLkvPGUeSwllMts+ITR6GIZFyOREERsKrN2vVWeUhsqZXt k=;
IronPort-PHdr: 9a23:bK8sBB889BouIv9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVceeBEb7K+PmRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BMAACeQA1d/5BdJa1kHAEBAQQBAQcEAQGBUwcBAQsBgRQvUANqVSAECyiEFoNHA4RSig9MgWoliUWJH4RUgS6BJANUCQEBAQwBARgBCgoCAQGEQAIXgkcjNAkOAQMBAQQBAQIBBW2KNwyFSgEBAQEDAQEQER0BASwMCwQCAQgRAwEBASsCAgIfBgsdCAIEARIigwABgR1NAx0BAgycQAKBOIhfcYExgnkBAQWBBgE/QYJ0DQuCEQMGgTQBi10XgUA/gTgME4JMPoIaRwEBAwGBfYJqMoImjkqEeYhTjQMsPwkCghKGTYkmg24bgiiHDI4SjSWHLYFtjWUCBAIEBQIOAQEFgVA4gVhwFTsqAYJBgkE3gzmFFIUIATZygSmOcQEB
X-IronPort-AV: E=Sophos;i="5.63,401,1557187200"; d="scan'208,217";a="579315855"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Jun 2019 20:42:16 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x5LKgG1Z029424 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 21 Jun 2019 20:42:16 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 21 Jun 2019 15:42:15 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 21 Jun 2019 15:42:14 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 21 Jun 2019 15:42:14 -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=lr4rlGV1CcVyQo7Z+NRJWZTrTJBYw2P5Eytoiu9IYPA=; b=A4da/Ct5js//guX1S7MWfXXaePY1soFooz2uQifs74gXBRUMedNDb1v5si6VsQOc/5vuGJzqv/HfXsOKFQ+4aY04rhyjShknFSkOsLuyO4gzMaA0ujrySo7x77sXY7QKDtsSVQUjPJP0BgQP8i03Q+2N+B3u52wMNDxiXUa2/vQ=
Received: from BYAPR11MB3255.namprd11.prod.outlook.com (20.177.184.148) by BYAPR11MB2648.namprd11.prod.outlook.com (52.135.227.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.12; Fri, 21 Jun 2019 20:42:13 +0000
Received: from BYAPR11MB3255.namprd11.prod.outlook.com ([fe80::a551:3737:e44d:2c5e]) by BYAPR11MB3255.namprd11.prod.outlook.com ([fe80::a551:3737:e44d:2c5e%5]) with mapi id 15.20.2008.007; Fri, 21 Jun 2019 20:42:13 +0000
From: "Aseem Choudhary (asechoud)" <asechoud@cisco.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "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"
Thread-Topic: The RTGWG WG has placed draft-asechoud-rtgwg-qos-model in state "Candidate for WG Adoption"
Thread-Index: AQHVJjqNFzKkxwtZpUqM/bSFnbn1SaamlncA//+LVQA=
Date: Fri, 21 Jun 2019 20:42:13 +0000
Message-ID: <BC7EE5F4-C564-4814-B2F7-D5283FEEDEB7@cisco.com>
References: <156090606508.6966.11992942280049135991.idtracker@ietfa.amsl.com> <00d401d52851$5eb240e0$4001a8c0@gateway.2wire.net> <e6b0d8b3-b842-4a9e-b502-fefa08f24e64@Spark>
In-Reply-To: <e6b0d8b3-b842-4a9e-b502-fefa08f24e64@Spark>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.9.190412
authentication-results: spf=none (sender IP is ) smtp.mailfrom=asechoud@cisco.com;
x-originating-ip: [2001:420:30d:1268:a537:870e:2820:81ac]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 11be6d7b-968b-4f08-abf3-08d6f688f0b3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2648;
x-ms-traffictypediagnostic: BYAPR11MB2648:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <BYAPR11MB2648414CDBBAA68CE803AFEEC2E70@BYAPR11MB2648.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0075CB064E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(366004)(376002)(346002)(39860400002)(13464003)(199004)(189003)(6512007)(2906002)(476003)(8936002)(53936002)(25786009)(73956011)(76176011)(99286004)(6306002)(54896002)(68736007)(5660300002)(229853002)(966005)(6116002)(36756003)(14454004)(316002)(110136005)(58126008)(33656002)(64756008)(6246003)(66446008)(71200400001)(71190400001)(478600001)(2501003)(81156014)(486006)(6506007)(66556008)(66946007)(8676002)(66476007)(186003)(11346002)(446003)(86362001)(2201001)(6486002)(6436002)(76116006)(46003)(256004)(7736002)(81166006)(102836004)(53546011)(2616005); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2648; H:BYAPR11MB3255.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: 9g1XXRZNLS9UvbdcIirJ4AGJl6guV75XEI7mzXYxsJVoAA5c3A0PVG53f7To+cqvIQIlOnoJqIs+O3yUC9cjiIzW31Tl+wFBDay/ZOxkCv8sQWkHILfIy+nTr7Po0yDltXh2Mbls4WsrLDCGvV4uChXazijY6Iruu0lR7ADxNS3/hJ2AuudvhQt6o8jaIg3jFcPg3/l2kK13z2aLE7a6BdUuVUUVutXx27zykRnCYJixMdBKxlu+kOOdlFJVPo2ET1AokWAN1kAy9wz5n2JS7EU4fPmzqGd7pW6ysKJ6Fmyg2xbjTRAcktK+W3y27aXuVZfh6BsyMRsDv17lULS6nFBi8yx7chyW+uj9klRyZjGPRoFYj+imefk4EPQ9U/Jdm2haGE0SClBaUa79C67xIucjyzT3SsUfqETFyVnUkvA=
Content-Type: multipart/alternative; boundary="_000_BC7EE5F4C5644814B2F7D5283FEEDEB7ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 11be6d7b-968b-4f08-abf3-08d6f688f0b3
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2019 20:42:13.2396 (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-CrossTenant-userprincipalname: asechoud@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2648
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/-GwwEEHvGZuzC74qzKEEeHEJYNU>
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: Fri, 21 Jun 2019 20:42:21 -0000

Hi Tom, Jeff,

We will be working on it before IETF105.

-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