IETF Logo Mail Archive

Re: [hybi] Multiplexing extension spec draft 03

"Arman Djusupov" <arman@noemax.com> Wed, 28 March 2012 06:48 UTC

Return-Path: <arman@noemax.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 620B621E80E7 for <hybi@ietfa.amsl.com>; Tue, 27 Mar 2012 23:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level:
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMT-4pYwPS5j for <hybi@ietfa.amsl.com>; Tue, 27 Mar 2012 23:48:39 -0700 (PDT)
Received: from mail.noemax.com (mail.noemax.com [64.34.201.8]) by ietfa.amsl.com (Postfix) with ESMTP id 5C03921E8126 for <hybi@ietf.org>; Tue, 27 Mar 2012 23:48:39 -0700 (PDT)
Received: from vista1 by mail.noemax.com (IceWarp 9.4.1) with ASMTP (SSL) id MJY17043; Wed, 28 Mar 2012 09:48:43 +0300
From: Arman Djusupov <arman@noemax.com>
To: 'Takeshi Yoshino' <tyoshino@google.com>, 'John Tamplin' <jat@google.com>
References: <CAH9hSJb1ewPO3EBgD78anD+=4XouToGR4X7C1wvWqonc2nYB6g@mail.gmail.com> <000301cd05dd$c8f9fc70$5aedf550$@noemax.com> <CAH9hSJYni6BboWdjkLX9xsguph7wJwjAmTUD1genFzT0ja5Wdw@mail.gmail.com> <003b01cd08d8$b1dd7050$159850f0$@noemax.com> <CAH9hSJYmL1ngaEJ1Th1kye2WKvJ4-zup1qbHCPLs+6MBOtS4Fg@mail.gmail.com> <001201cd0c06$3e9b3ab0$bbd1b010$@noemax.com> <CAH9hSJY1=KR-BrYUM-ACMVEVcb9+SMKH4fnoEfkyxu+6P4AwJA@mail.gmail.com> <002c01cd0c22$dd9e8fb0$98dbaf10$@noemax.com> <CABLsOLDz0tuz+mdwJj3XhG++QM5HgnVS=R0WFj+01UL9+HujWg@mail.gmail.com> <CAH9hSJY7i1xXQbOrqGCAiCon8NPNXQOTA4t5SBojh33=yJVoTA@mail.gmail.com>
In-Reply-To: <CAH9hSJY7i1xXQbOrqGCAiCon8NPNXQOTA4t5SBojh33=yJVoTA@mail.gmail.com>
Date: Wed, 28 Mar 2012 09:48:34 +0300
Message-ID: <002f01cd0cae$cff3b2f0$6fdb18d0$@noemax.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0030_01CD0CC7.F540EAF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJyksDj69tXg0EBn6jyTi4rbdnguwGRJ3ibAhBToZcCh7t1pgGkm8LGAowvP5UCsn+LAQFWWAl2AlZ0RF8CgcuNKpSaXqAg
Content-Language: en-us
Cc: hybi@ietf.org
Subject: Re: [hybi] Multiplexing extension spec draft 03
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 06:48:40 -0000

Yes, Thanks!  That is fine with me.

 

With best regards,

Arman

 

 

From: Takeshi Yoshino [mailto:tyoshino@google.com] 
Sent: Tuesday, March 27, 2012 6:48 PM
To: John Tamplin
Cc: Arman Djusupov; hybi@ietf.org
Subject: Re: [hybi] Multiplexing extension spec draft 03

 

OK. I will

- clarify that channel IDs are assigned by clients

- leave assignment algorithm up to implementations but warn that channel IDs
may be changed by intermediaries

but I will NOT

- add any constraint for intermediaries (so, intermediaries may reassign
channel IDs)

- explicitly expose channel ID to application layer (i.e. I won't add any
section like RFC 6455's section 12)

 

Are you fine with this, Arman?

v2.23.0 | Report a Bug | By Email