Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582bis
Tom Kristensen <tomkrist@cisco.com> Wed, 10 October 2012 08:52 UTC
Return-Path: <tomkrist@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 424D221F86F5 for <bfcpbis@ietfa.amsl.com>; Wed, 10 Oct 2012 01:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9I2prD5JWyM for <bfcpbis@ietfa.amsl.com>; Wed, 10 Oct 2012 01:52:35 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 27C8721F8585 for <bfcpbis@ietf.org>; Wed, 10 Oct 2012 01:52:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3997; q=dns/txt; s=iport; t=1349859155; x=1351068755; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rQwQ9sD/+eWC7p1adpUbynMDp+VXXlDuBqQvuNjJe4w=; b=UcJatkPGuqe24dBLDXIhSs8FALD5fSfMUvNl6xWozhcCokPKxUeiLuez 2AGQIYJE7aDP2wAJJhupazWymuALPDa1cQPk4ElkhkgTbvee6JamdMH65 DnckfmGSkNSvE61k9pk14cQpWA0FNRiYh9GoTudgTvuXD5A3ATctMHweq k=;
X-IronPort-AV: E=Sophos;i="4.80,564,1344211200"; d="scan'208";a="8675481"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 10 Oct 2012 08:52:34 +0000
Received: from [10.61.99.201] (dhcp-10-61-99-201.cisco.com [10.61.99.201]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q9A8qXTe000746; Wed, 10 Oct 2012 08:52:33 GMT
Message-ID: <50753751.1080305@cisco.com>
Date: Wed, 10 Oct 2012 10:52:33 +0200
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <92B7E61ADAC1BB4F941F943788C088280A5951@xmb-aln-x08.cisco.com> <C2BCA7974025BD459349BED0D06E48BB01286F70@MCHP03MSX.global-ad.net> <92B7E61ADAC1BB4F941F943788C088280DE72A@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C088280DE72A@xmb-aln-x08.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "Horvath, Ernst" <ernst.horvath@siemens-enterprise.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582bis
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Oct 2012 08:52:36 -0000
Actually, my proposal would be to move both the subsections under 6.2 "Unreliable Transport", since the "NAT Traversal" and "Large Message..."/"Fragmentation Handling" is written in the UDP/BFCP context. I also propose to collapse the section "Large Message..." and its subsection "Fragmentation Handling" into one, since the main thing here is to describe the fragmentation handling solution. OK? -- Tom On 10/08/2012 08:09 PM, Charles Eckel (eckelcu) wrote: > (as an individual) > > Hi Horvath, > > Sorry for the delay in responding. I agree that NAT traversal should not be a subsection of Large message considerations; however, I think it would be better to relocate it to section 6.2.3 as a part of Section 6.2 "Unreliable Transport". > > 6.2. Unreliable Transport . . . . . . . . . . . . . . . . . . . > 6.2.1. Congestion Control . . . . . . . . . . . . . . . . . . > 6.2.2. ICMP Error Handling . . . . . . . . . . . . . . . . . > 6.2.3. NAT Traversal . . . . . . . . . . . . . . . . . . . . > 6.3. Large Message Considerations . . . . . . . . . . . . . . . > 6.3.1. Fragmentation Handling . . . . . . . . . . . . . . . . > > Cheers, > Charles > > >> -----Original Message----- >> From: Horvath, Ernst [mailto:ernst.horvath@siemens-enterprise.com] >> Sent: Tuesday, September 25, 2012 3:29 AM >> To: Charles Eckel (eckelcu); bfcpbis@ietf.org >> Subject: RE: WGLC for draft-ietf-bfcpbis-rfc4582bis >> >> >> Currently 6.3.2 "NAT Traversal" is a subsection of 6.3 "Large Message >> Considerations". Is this really the intention, or should NAT Traversal better >> be renumbered as section 6.4? >> >> Regards, >> Ernst >> >> >>> -----Original Message----- >>> From: bfcpbis-bounces@ietf.org >>> [mailto:bfcpbis-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu) >>> Sent: Samstag, 22. September 2012 02:36 >>> To: bfcpbis@ietf.org >>> Subject: Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582bis >>> >>> Just a gentle reminder that we are into the last week for >>> comments. Please review the draft and submit your comments by >>> the Sept 28th, 2012 deadline (not 2011 as erroneously typed >>> previously) >>> >>> Thanks, >>> Charles (as co-chair) >>> >>> >>>> -----Original Message----- >>>> From: Charles Eckel (eckelcu) >>>> Sent: Friday, September 07, 2012 7:06 AM >>>> To: bfcpbis@ietf.org >>>> Subject: WGLC for draft-ietf-bfcpbis-rfc4582bis >>>> >>>> (As WG co-chair) >>>> >>>> This is to announce a working group last call for >>>> >>> draft-ietf-bfcpbis- >>> >>>> rfc4582bis, "The Binary Floor Control Protocol (BFCP)". >>>> http://datatracker.ietf.org/doc/draft-ietf-bfcpbis-rfc4582bis/ >>>> >>>> This is intended as a Standards Track RFC, obsoleting RFC 4582. >>>> Please respond to the list by September 28th 2011 (i.e. 3 >>>> >>> weeks) with any >>> >>>> comments. >>>> >>>> It is helpful to attempt to categorize your comment (e.g. >>>> >>> technical issue vs. >>> >>>> editorial), and also to provide any replacement text you >>>> >>> feel is necessary. >>> >>>> If you review the document and have no comments, please >>>> >>> tell the chairs >>> >>>> that you have reviewed it. This is always useful >>>> >>> information in assessing the >>> >>>> degree of WG review and consensus behind the document. >>>> Note, another WGLC for draft-ietf-bfcpbis-rfc4583bis will >>>> >>> be run in parallel. >>> >>>> Cheers, >>>> 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 >
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Charles Eckel (eckelcu)
- [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582bis Charles Eckel (eckelcu)
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Mary Barnes
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Charles Eckel (eckelcu)
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Horvath, Ernst
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Charles Eckel (eckelcu)
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Tom Kristensen
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Tom Kristensen
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Tom Kristensen
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Charles Eckel (eckelcu)
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Charles Eckel (eckelcu)
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Gonzalo Camarillo
- Re: [bfcpbis] WGLC for draft-ietf-bfcpbis-rfc4582… Tom Kristensen