Re: [Teas] Mirja Kühlewind's Discuss on draft-ietf-teas-rsvp-te-scaling-rec-06: (with DISCUSS and COMMENT)

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Thu, 05 October 2017 11:57 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A991342DD for <teas@ietfa.amsl.com>; Thu, 5 Oct 2017 04:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.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 IxgXGE-bivx3 for <teas@ietfa.amsl.com>; Thu, 5 Oct 2017 04:57:46 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B2B613454B for <teas@ietf.org>; Thu, 5 Oct 2017 04:57:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net; b=ouXc8GUlQhlfR1IEQnjM8lWrSCgkh4U0jntKEhK53MnQQpI72Amj+ksN7PFGRhhRtwQ3x+vd9GSGkaThwd55p4QmIV5DOT3TqSDsPOieX8lTozeUL6MwvPyFKR6LofIUXFVRq88GCTQEYSlKftzrgV/NcLbNcwDWxNXwN5dPZS0=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 17559 invoked from network); 5 Oct 2017 13:57:42 +0200
Received: from pd9e119f3.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.25.243) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 5 Oct 2017 13:57:42 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <CA+YzgTtqT9Ojs8Ed8fwW3FCLGVaJMTgCxsonH1Gxe-H7Q85orA@mail.gmail.com>
Date: Thu, 05 Oct 2017 13:57:41 +0200
Cc: draft-ietf-teas-rsvp-te-scaling-rec@ietf.org, TEAS WG Chairs <teas-chairs@ietf.org>, The IESG <iesg@ietf.org>, "teas@ietf.org" <teas@ietf.org>, Lou Berger <lberger@labn.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBCF6104-8351-4C90-BD38-6A515DCAB9E5@kuehlewind.net>
References: <150644890311.20830.6212136664552694640.idtracker@ietfa.amsl.com> <CA+YzgTtqT9Ojs8Ed8fwW3FCLGVaJMTgCxsonH1Gxe-H7Q85orA@mail.gmail.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20171005115742.17550.34578@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/caPkzzN62Z3NcX09TNMYq1h6c1k>
Subject: Re: [Teas] Mirja Kühlewind's Discuss on draft-ietf-teas-rsvp-te-scaling-rec-06: (with DISCUSS and COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Oct 2017 11:57:48 -0000

Hi Pavan,

I don’t see any changes in the new version that addresses may actual discuss on section 2.1.3 (now section 2.3). Can you please clarify?

Thanks,
Mirja


> Am 28.09.2017 um 05:45 schrieb Vishnu Pavan Beeram <vishnupavan@gmail.com>:
> 
> Mirja, Hi!
> 
> Thanks for the review. We just posted a new revision (-07) to address the Gen-Art review comments. Please go through the new diffs (https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-rsvp-te-scaling-rec-07) and let us know if additional changes are required. 
> 
> Also, please go through the responses provided to the other review comments and let us know if there are still any unanswered questions.
> 
> Regards,
> -Pavan
> 
> 
> 
> On Tue, Sep 26, 2017 at 2:01 PM, Mirja Kühlewind <ietf@kuehlewind.net> wrote:
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-teas-rsvp-te-scaling-rec-06: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-teas-rsvp-te-scaling-rec/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I'm uncertain what section 2.1.3. actually recommends. My understanding is that
> it is recommend to still send retransmit some message even if the Rl was
> reached and to that every 30s basically forever. First of all I think this
> still needs a termination criteria when to stop to try to retransmit finally.
> And the I don't understand why this is needed, instead of e.g. just using a
> larger Rl value? Can you please clarify!
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I fully agree with the gan-art review (Thanks Elwyn!) and Alvaro, that this
> reads from time to time like a BCP but is actually a extension specification. I
> would strongly recommend to apply the changes proposed by the gen-art review,
> and there is also a very detailed list of nits/edits that should probably be
> applied. Please have a look at that!
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>