Re: [hybi] RSV bits in extensions

Takeshi Yoshino <tyoshino@google.com> Mon, 21 May 2012 07:46 UTC

Return-Path: <tyoshino@google.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 D035721F85B5 for <hybi@ietfa.amsl.com>; Mon, 21 May 2012 00:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 zn3Nc0PawKM8 for <hybi@ietfa.amsl.com>; Mon, 21 May 2012 00:46:22 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4539D21F84A6 for <hybi@ietf.org>; Mon, 21 May 2012 00:46:22 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so365668ghb.31 for <hybi@ietf.org>; Mon, 21 May 2012 00:46:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=XtQtz2HViXYfkGGtC7Oo3S30MCsTkRvpGOHnehLLGtw=; b=hpaabQSo5sRVPPvWyJCT9qsaQzTugOx/aXoTny7Pi7T4hlOFWZCkkssgfFX00zOEfl oLas8Hyt2562wE68TvkXfrGoz02My8WpkINQ/myz8p2xO2SMcn+bPCyjwcEEYr8Pok+F FqYp7pyo9BQ/wTRfSrrwZrfPPNzFk5s6Ctkz4zo0bAeeYlfY8X1PHyQLjbolblaXdWkc F1IdCFcf8KqqDVpIKF/9lXhpBPclF9UfmdCk6B4FQuZCzaMb1znQbwJnANDOvN3hYE0G 70c9r5uDXrW9Dxr/H98mcjssNgW0SES5M+KKvFdBytkUtTdwqMv3ci/+bk4IYvv4IdW8 LQYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=XtQtz2HViXYfkGGtC7Oo3S30MCsTkRvpGOHnehLLGtw=; b=ESoIZNLQ+7HPZS3y2MVeOCdNUOnLG6TNCVPghIxT+nkhJrfp4Uew05EzsT0Ova0Pui ENSh4JH6bv09qUcm2wlZq8sf0ft8nGNC18s3vv8lxYmV80D9DLZ1RS4dRaRIH5Eci7bN eoBXaxXka464sg2APgb4A/OBoTYgoextSUd7/pUJ1NaCDyAOiQMctzNpKF5ZWXDsevws aW/jIZ43w1vFofqGRrb2FMkb227m/nydeJiIlU/1YnfAvJu53brVRsqhgLp3osUrXqH7 I4XNmTGFoRyWoySqS5AQyCUbiaV/EWJlpnOBwlWPt+oSLh7GH+9dQnmOyK/Gcw9Ytu5X 59lw==
Received: by 10.50.222.137 with SMTP id qm9mr5923226igc.64.1337586381410; Mon, 21 May 2012 00:46:21 -0700 (PDT)
Received: by 10.50.222.137 with SMTP id qm9mr5923221igc.64.1337586381304; Mon, 21 May 2012 00:46:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.112.130 with HTTP; Mon, 21 May 2012 00:46:00 -0700 (PDT)
In-Reply-To: <D212E3B5-0DB8-4F52-B16F-A4B5D89F932E@zaphoyd.com>
References: <D212E3B5-0DB8-4F52-B16F-A4B5D89F932E@zaphoyd.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 21 May 2012 16:46:00 +0900
Message-ID: <CAH9hSJZxCcntP6SCL176jcEi_2b_EfYLhhnHE25t9fr1KGb5gw@mail.gmail.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary="14dae93410731d32bc04c0871949"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQm4m5Pz6AM4yC2w/h2/olegD63zJJAlKxnpgcOwj22xq42x3WKMOehVZCQIXdVZPLmJJUftLFNNMeI+gWYFmxCPxG+cFOUPVMgOX7zb6Ad9gK4/YKZWe/+jBf1FS8wABlAJz3bY
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] RSV bits in extensions
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: Mon, 21 May 2012 07:46:22 -0000

On Sat, May 12, 2012 at 2:24 AM, Peter Thorson <webmaster@zaphoyd.com>wrote:

> Is the intention of the RSV registration to prevent the reuse of RSV bits
> or simply to catalog their use and help determine potential conflicts?
>

My understanding is
- it's to get the allocation widely known to prevent unexpected
confliction, complication.
- it doesn't disallow use of the same bit by multiple extensions completely.


> In the case that an endpoint gets a handshake request for two extensions
> with incompatible RSV bit registrations what is the expected behavior? Just
> pick one? Return an incompatible extension code? Return protocol error?
> Something else?
>

I think
- it's ok to request two or more mutually incompatible extensions
- it's ok that the server accept the client by picking one of them.
- if the client requested two or more mutually incompatible extensions and
the server acked two or more of them, the client must fail.

Takeshi