Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)

"Susan Hares" <shares@ndzh.com> Sat, 28 January 2017 15:39 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83AC3129570; Sat, 28 Jan 2017 07:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no 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 tu0ignJY4bvi; Sat, 28 Jan 2017 07:39:38 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2960A129571; Sat, 28 Jan 2017 07:39:38 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.161.15;
From: "Susan Hares" <shares@ndzh.com>
To: "'Job Snijders'" <job@instituut.net>, "'Jeffrey Haas'" <jhaas@pfrc.org>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org> <CADLW2vwFPikHb9=+V7oQ-HTQPu+s1S5e_B0x8yai8wLB-4z6Tw@mail.gmail.com> <20170128020205.GA3201@pfrc.org> <20170128120217.GA91223@Vurt.local> <20170128121025.GB91223@Vurt.local>
In-Reply-To: <20170128121025.GB91223@Vurt.local>
Date: Sat, 28 Jan 2017 10:35:17 -0500
Message-ID: <018601d2797c$21320ec0$63962c40$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIhUUJZA+cIT4/8zl2Sev/afC8NdAJB2HE6AUlHwPsCoauwKwGZAsXWAaYzxQygZPVe4A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/uLUHl6Do-rA7N1Frv4TOJuZFKf4>
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jan 2017 15:39:39 -0000

Job: 

Thanks for letting me know.  Please put up the implementation changes once
you have the reset in a draft.  Without out it, we'd will be blocked to send
this to the IESG.

Sue 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders
Sent: Saturday, January 28, 2017 7:10 AM
To: Jeffrey Haas
Cc: idr@ietf.org; draft-ietf-idr-shutdown@ietf.org; Susan Hares
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to
1/31/2017)

BTW, regarding last call & IDR implementation requirements, i can
immediately deliver at least two implementations that also accomodate the
'reset' case so from that perspective there will be no blocker to proceed.

Kind regards,

Job

On Sat, Jan 28, 2017 at 01:02:17PM +0100, Job Snijders wrote:
> Hi group,
> 
> On Fri, Jan 27, 2017 at 09:02:05PM -0500, Jeffrey Haas wrote:
> > On Fri, Jan 27, 2017 at 03:21:19PM -0800, Matthew Walster wrote:
> > > On 27 January 2017 at 13:38, Jeffrey Haas <jhaas@pfrc.org> wrote:
> > > 
> > > > I believe the draft should cover both administrative sub-codes.
> > > > [...] Suggestions of other cases to expand the text-form of the 
> > > > notification to other sub-codes.
> > 
> > > There is obvious scope-creep at this point, I would like to 
> > > suggest either the draft considered as-is or to allow all Cease 
> > > sub-codes to have shutdown communication possible.
> > 
> > I certainly hadn't intended to try to push for a more general 
> > widening of the scope; just point out something under the existing use
case.
> > 
> > While you give three other examples of places that could benefit 
> > from additional data regarding why the session has been sent a 
> > CEASE, I don't think all of them are equally clear with respect to 
> > that data being text.
> > 
> > As an example, the max prefixes might benefit from a simple tuple.
> > E.g. AFI,SAFI,<limit>. Although keeping this within even a 
> > light-weight TLV would permit space for the machine-readable portion 
> > along with a human readable one.
> > 
> > I would suggest in the absence of a strong case for text strings in 
> > the other sub-codes that for now the draft stay restricted to the 
> > administrative reset cases. As this draft proves, if there's 
> > consenus to add additional DATA to one of the code points, it can move
fast.
> 
> I think Jeff's suggestion to add the Administrative Reset (subcode 4) 
> case is a good one. There can be value in attachting contact 
> information or a case identifier to BGP resets. Matthew mentioned 
> (outside of this mailing list) that this information would especially 
> be useful if after the reset, the BGP session does not re-establish. 
> Also, conceptually the 'reset' and 'shutdown' are close to each other 
> as they are initiated by the Administrator.
> 
> However, I consider the other subcodes out of scope for what 
> draft-ietf-idr-shutdown tries to accomplish, and as such would belong 
> in their own Internet-Draft.
> 
> Kind regards,
> 
> Job

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr