[hybi] RSV bits in extensions

Peter Thorson <webmaster@zaphoyd.com> Fri, 11 May 2012 17:24 UTC

Return-Path: <webmaster@zaphoyd.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 5BB4D21F8675 for <hybi@ietfa.amsl.com>; Fri, 11 May 2012 10:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.657
X-Spam-Level:
X-Spam-Status: No, score=0.657 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 gLAJMtUww7QC for <hybi@ietfa.amsl.com>; Fri, 11 May 2012 10:24:14 -0700 (PDT)
Received: from sh78.surpasshosting.com (sh78.surpasshosting.com [72.29.64.142]) by ietfa.amsl.com (Postfix) with ESMTP id 772BB21F867E for <hybi@ietf.org>; Fri, 11 May 2012 10:24:14 -0700 (PDT)
Received: from 143.sub-166-249-128.myvzw.com ([166.249.128.143]:14749 helo=[10.167.111.29]) by sh78.surpasshosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <webmaster@zaphoyd.com>) id 1SStZc-0004Gf-Hd for hybi@ietf.org; Fri, 11 May 2012 13:24:13 -0400
From: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-9683C305-E7B6-4D61-88F8-CEEE27C6C3EF"
X-Mailer: iPad Mail (9B176)
Message-Id: <D212E3B5-0DB8-4F52-B16F-A4B5D89F932E@zaphoyd.com>
Date: Fri, 11 May 2012 12:24:01 -0500
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sh78.surpasshosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - zaphoyd.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: [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: Fri, 11 May 2012 17:24:15 -0000

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?

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?

Peter Thorson