Design: Frame type extensibility issues

James M Snell <> Sat, 11 May 2013 16:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EDA3B21F8EAE for <>; Sat, 11 May 2013 09:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.417
X-Spam-Status: No, score=-10.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LaZAVcCr8CJ6 for <>; Sat, 11 May 2013 09:18:14 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 8E55E21F8EAD for <>; Sat, 11 May 2013 09:18:14 -0700 (PDT)
Received: from lists by with local (Exim 4.72) (envelope-from <>) id 1UbCTu-0000O4-OY for; Sat, 11 May 2013 16:17:10 +0000
Resent-Date: Sat, 11 May 2013 16:17:10 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtp (Exim 4.72) (envelope-from <>) id 1UbCTk-0000NH-0a for; Sat, 11 May 2013 16:17:00 +0000
Received: from ([]) by with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <>) id 1UbCTj-0003yq-Eg for; Sat, 11 May 2013 16:16:59 +0000
Received: by with SMTP id k14so4431570oag.8 for <>; Sat, 11 May 2013 09:16:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=yQTIhNYZaKDx/g/UEVAGOA0xUaQuI7UuJPXQB50QVwQ=; b=tglEhtZUa6fo2lpiL+mlAv/0uUjyqc6Usil+iaRBroJo3Dd07748ktHnBwjDpExVRt yDpZQ3Svp1GXTQDNDDMhW7EUD8ZRumf0fhG+SQs4nXtae6ajDJ7JZAYJ0dl4hYgLIrFF 4q5FfEuQaQgJkwdQ5s58VrqIaAl7G15fRjHYinZSCdiSE/s2CKzxUw675W3YfMwRlP2A QGYwQg/Zk+bRrmUA+DIJRpkbJFYOoVU6pAjhaGcgkSrDRzDlOmAtkhwRKzb3IrOa9lqX 04oR3HYVrsnyJDy2Q/ev2o0GLWq8rF9NTwgjsRR/sNrChq0dUELawjUGdxQeVZUAgtv2 j9ww==
X-Received: by with SMTP id b17mr1482201oen.63.1368288993567; Sat, 11 May 2013 09:16:33 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sat, 11 May 2013 09:16:13 -0700 (PDT)
From: James M Snell <>
Date: Sat, 11 May 2013 09:16:13 -0700
Message-ID: <>
To: "" <>
Content-Type: text/plain; charset=UTF-8
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.692, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: 1UbCTj-0003yq-Eg 58a7c0ac894e8b557697755f6e4011dc
Subject: Design: Frame type extensibility issues
Archived-At: <>
X-Mailing-List: <> archive/latest/17950
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

(btw, I'm posting these so that the issues are documented.. if there's
no time to discuss these issues now, or if it makes more sense to
discuss them later on in the process, that's obviously perfectly fine)

There are a couple of issues relating to frame type extensibility:

1. Are frames end-to-end or hop-by-hop? This is currently undefined.
Control frames appear to always be hop-by-hop, Header bearing frames
might or might not be hop-by-hop, Data frames appear to always be
end-to-end. What about new extension frame types?

2. Are new unsupported frame types subject to flow control? How can we
differentiate new control frame types vs. data frame types?

3. There is no prescribed mechanism for rolling out support for new
standard frame types vs. private use frame types.


One approach we can take to dealing with this is to segment the 8-bit
frame type namespace into two distinct categories and reserve a
limited number of frame types from each for "private use". That is,

0xxxxxxx => Control Frames
1xxxxxxx => Data Frames

Control Frames (0x00-7F) are always hop-by-hop and are not subject to
flow control. Frame types 0x6B-7F would be reserved for "private use",
meaning that these types could not be registered within the IANA

Data Frames (0x80-FF) are always end-to-end and are subject to flow
control. Frame types 0xEB-FF would be reserved for "private use".

The frame type of the existing DATA frame would change from 0x00 to
0x80, all other existing frame types would remain unchanged.

This approach gives us a clear way of dealing with extension frames,
flow control, etc without introducing undue complexity.