Re: [bfcpbis] call for comments on draft-ietf-bfcpbis-rfc4583bis
"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 19 March 2014 22:28 UTC
Return-Path: <eckelcu@cisco.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 AE5651A023C for <bfcpbis@ietfa.amsl.com>; Wed, 19 Mar 2014 15:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level:
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 jyy5t7hcxRAx for <bfcpbis@ietfa.amsl.com>; Wed, 19 Mar 2014 15:28:13 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 778561A0761 for <bfcpbis@ietf.org>; Wed, 19 Mar 2014 15:28:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1334; q=dns/txt; s=iport; t=1395268084; x=1396477684; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=5M+7ia7ukD7DpKlO8whEOOzUeno3vRmAVBj/LfuuNK4=; b=PiN3EctsBX9kcmnfC3Y+82TSBwLfAsMBxvF5wWVetcrTyMvr+lyNNQg9 Vr6PQnoeKOgK5OqwPwt8EMjMG5fEzAm603VyoRtSwD/RBfkDAEYnPNvS0 LJG9vkU830+w4H4a6sD32pPqn1lKSl9ObF7WlUz4ECmyD2Gz2MH+Zzfr2 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am4GALEZKlOtJV2c/2dsb2JhbABagwY7TAu7FoZjgW8WdIInAQQBAQEaUR0BCG0LJwQBEod4AQ3QMBeTJASJGo8tgTKQfoMtgis
X-IronPort-AV: E=Sophos;i="4.97,689,1389744000"; d="scan'208";a="311493398"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 19 Mar 2014 22:27:44 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2JMRgx0021924 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <bfcpbis@ietf.org>; Wed, 19 Mar 2014 22:27:42 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.148]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Wed, 19 Mar 2014 17:27:42 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: [bfcpbis] call for comments on draft-ietf-bfcpbis-rfc4583bis
Thread-Index: AQHPQ8JxVQNELiQ44kaCH6k37ugk+w==
Date: Wed, 19 Mar 2014 22:27:42 +0000
Message-ID: <CF4F6225.2322E%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [171.68.20.15]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F4F84C2DCFC13A4A915B553CB6ED56DC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/bfcpbis/ij3FWQF-Zo5pCv2A57O1WbJrGsQ
Subject: Re: [bfcpbis] call for comments on draft-ietf-bfcpbis-rfc4583bis
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, 19 Mar 2014 22:28:22 -0000
(as an individual) I read through the draft in detail. It addresses all the concerns I raised previously. I would to suggest a few additional changes. These are mostly editorial. Section 1 s/This data include/This data includes Section 7 s/and, when acting as a floor control server to use/and, when acting as a floor control server, to use Section 8 s/will direct the BFCP messages/direct the BFCP messages Section 9 s/How to determine which endpoint to initiate/How to determine which endpoint initiates Section 13 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-rfc4583bis-09 >(http://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4583bis-09), 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] 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