RE: WG last call for draft-ietf-rtgwg-uloop-delay

Chris Bowers <cbowers@juniper.net> Sun, 04 June 2017 16:47 UTC

Return-Path: <cbowers@juniper.net>
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 2F9BE1252BA for <rtgwg@ietfa.amsl.com>; Sun, 4 Jun 2017 09:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.121
X-Spam-Level:
X-Spam-Status: No, score=-0.121 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 zqyx8WUdyveq for <rtgwg@ietfa.amsl.com>; Sun, 4 Jun 2017 09:47:34 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0120.outbound.protection.outlook.com [104.47.41.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B721200B9 for <rtgwg@ietf.org>; Sun, 4 Jun 2017 09:47:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vzw3vEBEM1ETUt4jfHIQo9mDrKsfJJx08OSSZGcG+14=; b=ZbdP/DvLfm2iOY2kH2dl7NLW4wvoGExgjNsLK/HeuNSu/jSS3lJ+HfOwXeWnkJr3TtMVgdKUnsr0W/RQHsYQJtsPYRtONR3UA7wT7AyCtT8ddvyerlY3td3Ly/4ilnhvpbOHs/UTGEAj8KoxMoq5M0xyNMYrtUAEmqrHhlRw8nk=
Received: from MWHPR05MB2829.namprd05.prod.outlook.com (10.168.245.11) by MWHPR05MB2832.namprd05.prod.outlook.com (10.168.245.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.6; Sun, 4 Jun 2017 16:47:32 +0000
Received: from MWHPR05MB2829.namprd05.prod.outlook.com ([10.168.245.11]) by MWHPR05MB2829.namprd05.prod.outlook.com ([10.168.245.11]) with mapi id 15.01.1143.018; Sun, 4 Jun 2017 16:47:33 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "Acee Lindem (acee)" <acee@cisco.com>, RTGWG <rtgwg@ietf.org>
Subject: RE: WG last call for draft-ietf-rtgwg-uloop-delay
Thread-Topic: WG last call for draft-ietf-rtgwg-uloop-delay
Thread-Index: AdLb3vVB+stvjRstQSySgkSfkwvpZAA3sw0AACSrRQA=
Date: Sun, 04 Jun 2017 16:47:32 +0000
Message-ID: <MWHPR05MB28296990E1AEB0A5ADA98BBFA9F50@MWHPR05MB2829.namprd05.prod.outlook.com>
References: <MWHPR05MB2829DC391A9101895C1D297FA9F70@MWHPR05MB2829.namprd05.prod.outlook.com> <D558B7A5.B2045%acee@cisco.com>
In-Reply-To: <D558B7A5.B2045%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.239.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR05MB2832; 7:ypzlWW7/MqmE58kUXk5Q/h7DDbHaSUN1rc7pdYrmjstImyoKImnAK6raBt3nqs1iMvKgrmcuo5dN+dxMyn5dleFsPQ2AfSHKqqCazNM8xE9SOA4DYFto/z7fhW08fMZR5Ja+hqTKw+XAt4AMO5vmDvJ0LaiWSdUOzshiq0wmNDfzDQ/6IBUoh+tejZ8so7YmQyTbhZ+G+FkB250/X94ia5TGoLDZIsjXlLkSEpxsnc6pwZHdJflscO8TwSgePmUIt7dN5cMfro1QqydX9EFcDwDbo7xH4cTmqVcTq2HlDkUnS3Ri9cLlbTBRexzShY9boJEL2mzlfHstu91+KN6AoQ==
x-ms-traffictypediagnostic: MWHPR05MB2832:
x-ms-office365-filtering-correlation-id: 79e34ccb-7e8e-4588-9b1c-08d4ab696595
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:MWHPR05MB2832;
x-microsoft-antispam-prvs: <MWHPR05MB283260E29A1E0AE2277D7AA0A9F50@MWHPR05MB2832.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(138986009662008)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:MWHPR05MB2832; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:MWHPR05MB2832;
x-forefront-prvs: 03283976A6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39450400003)(39840400002)(39410400002)(39850400002)(39860400002)(39400400002)(377454003)(2900100001)(9686003)(236005)(54896002)(6306002)(66066001)(7696004)(6506006)(6246003)(38730400002)(2950100002)(7736002)(6436002)(86362001)(53936002)(77096006)(122556002)(74316002)(7906003)(25786009)(5660300001)(53546009)(606005)(966005)(55016002)(8676002)(229853002)(189998001)(81166006)(99286003)(8936002)(33656002)(54356999)(50986999)(76176999)(14454004)(3846002)(6116002)(102836003)(790700001)(478600001)(3660700001)(230783001)(3280700002)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB2832; H:MWHPR05MB2829.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR05MB28296990E1AEB0A5ADA98BBFA9F50MWHPR05MB2829namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2017 16:47:32.9190 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB2832
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/8CuDgs7BbgvaOc_MPaCoUUVMJ20>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
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, 04 Jun 2017 16:47:37 -0000

As a WG participant, I think standards track makes most sense, since it specifies a precise behavior for a router under certain conditions.  It is likely that network operators and software implementers will want to use the document as a means of communicating about whether or not a given implementation supports that precise behavior.  In my opinion, a standards track document is the best format to support that interaction.

Chris

From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Saturday, June 3, 2017 6:05 PM
To: Chris Bowers <cbowers@juniper.net>; RTGWG <rtgwg@ietf.org>
Subject: Re: WG last call for draft-ietf-rtgwg-uloop-delay

I support advancement and publication of this draft.  I think we should have the discussion of whether or not it should be standards track, BCP, or informational as invariably this question will arise during all the reviews.
Thanks,
Acee

From: rtgwg <rtgwg-bounces@ietf.org<mailto:rtgwg-bounces@ietf.org>> on behalf of Chris Bowers <cbowers@juniper.net<mailto:cbowers@juniper.net>>
Date: Friday, June 2, 2017 at 4:43 PM
To: Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: WG last call for draft-ietf-rtgwg-uloop-delay

RTGWG,

This email starts the two week WG last call for draft-ietf-rtgwg-uloop-delay.

https://datatracker.ietf.org/doc/draft-ietf-rtgwg-uloop-delay/

Please indicate support for or opposition to the publication of this
standards track document, along with the reasoning for that support or
opposition.

IPR:
If you are listed as a document author or contributor, please respond to
this email stating whether or not you are aware of any relevant IPR. The
response needs to be sent to the RTGWG mailing list. The document will
not advance to the next stage until a response has been received from
each author and each individual that has contributed to the document.

The document currently has the following IPR disclosure associated
with it.
https://datatracker.ietf.org/ipr/2565/

This last call will end on Friday June 16th.

Thanks,
Chris and Jeff