Re: [bfcpbis] call for comments on draft-ietf-bfcpbis-rfc4582bis
Tom Kristensen <2mkristensen@gmail.com> Wed, 16 April 2014 16:44 UTC
Return-Path: <2mkristensen@gmail.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 679E81A0243 for <bfcpbis@ietfa.amsl.com>; Wed, 16 Apr 2014 09:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 C08eTE2iMHKe for <bfcpbis@ietfa.amsl.com>; Wed, 16 Apr 2014 09:44:46 -0700 (PDT)
Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 432991A01F2 for <bfcpbis@ietf.org>; Wed, 16 Apr 2014 09:44:46 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id m5so8842580qaj.20 for <bfcpbis@ietf.org>; Wed, 16 Apr 2014 09:44:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jfFJVgVJWithzzes8vrjua1WSThWLvKVP3lJZSCTzGE=; b=xbJoDEiSGDHqxCx7sAbhfpi+zh5uVFeLh8ptFiryI+CInK9Wjc97CPa/km/88eQeYB 5qLGzPTwTL4Bt+lP7d+XTLmv+1sI1EwZlbui1ADmHZ9nZdWUogohTmqyv1T+5WdgamTG wkbxqXxqmeml0BX7Pbcr9OwekEz0lu/MjfJ6mO9OyWGOVkNZyoarZRgrZZCoZcxjoRO6 Q/VD+z9DtGZ/06oJeO9NLLjgpPzm04NLlc1ojjy+AOOpHm2efhyUft9C9+jGQJkEOYsO 4tNxCIqhlpyoA1n8LE1LvOJ6uu6uIzByrtb8yB9xM7g7nd2BhWYhNFFwdkmDoIRod36W cYhQ==
MIME-Version: 1.0
X-Received: by 10.224.13.76 with SMTP id b12mr6430977qaa.34.1397666682747; Wed, 16 Apr 2014 09:44:42 -0700 (PDT)
Received: by 10.229.2.66 with HTTP; Wed, 16 Apr 2014 09:44:42 -0700 (PDT)
In-Reply-To: <CF4F47D5.2317A%eckelcu@cisco.com>
References: <CF4F47D5.2317A%eckelcu@cisco.com>
Date: Wed, 16 Apr 2014 18:44:42 +0200
Message-ID: <CAFHv=r__nvwkSw5TYzC9SXh753oasWe_EzAr-K4KQ5iU=Hv=rQ@mail.gmail.com>
From: Tom Kristensen <2mkristensen@gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Content-Type: multipart/alternative; boundary="047d7bdc831c23f40904f72ba285"
Archived-At: http://mailarchive.ietf.org/arch/msg/bfcpbis/6fW2XDkShQxYSiqB3e-EvzDEbW4
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] call for comments on draft-ietf-bfcpbis-rfc4582bis
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 16:44:51 -0000
Thanks, Charles! Also for this draft, a native English speaker and writer is very much appreciated. All issues fixed accordingly to the suggestions. -- Tom On 19 March 2014 23:27, Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote: > (as an individual) > > I read through the draft in detail. It addresses all the concerns I raised > previously. > In addition to the TCP/TLS clarifications requested by Christer, I suggest > the following changes. These are mostly editorial. > > Section 5.3.17: > s/should acknowledge/acknowledge > I think it is best to drop the ³should² to avoid confusion with normative > statements. This is also more consistent with the rest of the message > descriptions in this section. Normative language regarding the sending of > request/response messages is specified elsewhere. > > Section 6: Transport > I suggest rewording the information note as follows: > OLD: > Informational note: In practice products are configured to try one > transport initially and use the other one as a fallback. > Whether > TCP or UDP is chosen as underlying transport depends on type > of > product and the nature of the environment it is deployed. > Here > Appendix B are important to consider. > > NEW: > Informational note: In practice, products are configured to try one > transport first and use the other transport as a fallback. > Whether > TCP or UDP is chosen as the underlying transport depends on > the type of > product and the deployment environment. See Appendix B for > additional > considerations. > > > Section 6.2 > s/Situations Š is described/Situations Š are described > > Section 8 > s/all requests will use retransmission timer T1/retransmission timer T1 > MUST be used for all requests > > Section 8.2 > s/valuse/values > > Section 16.2 > s/The clarification and bug fixes/Clarifications and bug fixes > > > I¹m not sure what "Non-functional language clarifications² are, but I > don¹t think we want them in the draft :) > Perhaps replace with ³Non-normative language clarifications²? > > > Cheers, > Charles > > > On 3/4/14, 3:06 PM, "Charles Eckel (eckelcu)" <eckelcu@cisco.com> wrote: > > >As discussed in the session today at IETF 89, this is to officially > >announce a 2-week call for comments on draft-ietf-bfcpbis-rfc4582bis-11 > >(http://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4582bis-11), due by or > >before March 19, 2014. > >If the draft is perfect as is, please share that comment on the list as > >well. > > > >Thank you, > >Charles > > > > > >_______________________________________________ > >bfcpbis mailing list > >bfcpbis@ietf.org > >https://www.ietf.org/mailman/listinfo/bfcpbis > > _______________________________________________ > bfcpbis mailing list > bfcpbis@ietf.org > https://www.ietf.org/mailman/listinfo/bfcpbis > -- # Cisco | http://www.cisco.com/telepresence/ ## tomkrist@cisco.com | http://www.tandberg.com ### | http://folk.uio.no/tomkri/
- [bfcpbis] call for comments on draft-ietf-bfcpbis… Charles Eckel (eckelcu)
- Re: [bfcpbis] call for comments on draft-ietf-bfc… Charles Eckel (eckelcu)
- Re: [bfcpbis] call for comments on draft-ietf-bfc… Tom Kristensen