IETF Logo Mail Archive

[Cellar] On the multiplicity of Info elements

Michael Bradshaw <mjbshaw@google.com> Tue, 29 December 2015 22:28 UTC

Return-Path: <mjbshaw@google.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C6B1A8A87 for <cellar@ietfa.amsl.com>; Tue, 29 Dec 2015 14:28:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k56vaFaWsJ8n for <cellar@ietfa.amsl.com>; Tue, 29 Dec 2015 14:28:02 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 373A51A8A86 for <cellar@ietf.org>; Tue, 29 Dec 2015 14:28:02 -0800 (PST)
Received: by mail-pa0-x235.google.com with SMTP id yy13so37131262pab.3 for <cellar@ietf.org>; Tue, 29 Dec 2015 14:28:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=5u8bC5KGc29tpI2tMLN0RN6Kp7fZ4nv0w9xGx3noYGo=; b=LlkCBbPrbS7r9gl2R9eThMojxJZLP3nmTxFIVIh3OYGssudBRZ467bJS/XbWwAfri4 ZrLzEOsI9FOPZ0umE/zsgnWNCWx1NHY2yBEU+i2BzKlOS+sXHOv0Rks4LhpqN0QTIobG Ez0I8BBp2FMHnCoWK+mp8w8vLqfxA/1Mi5Y/l+9UuWY6m5afcltkiovsG3o5m7gQBbyX yFo8/lJEdFJYDRDkCUajIN1/zEOuA9xhmFwYAbwmayaBaInJwjpautYn1lYnyv8zq0dJ jW/7Tvs7cmhrhDPP1OeDYQ06HsxKYmEBljGOCbynfGU8uKBB+0qqBhir7x82v0Q5m7GE VBkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=5u8bC5KGc29tpI2tMLN0RN6Kp7fZ4nv0w9xGx3noYGo=; b=COQ1dhug9S2U93IWyTeKeJoIbivjqRl5sniR/JBrD0dFobr9EZVYgpmdXfXgNvogj7 +iKHILzyGh0mxJ6FlIQjP3fNlIEguSJ304RdiFtwgrhzL0tEJPD0CXFBYz+lDXtaidfv lxDPWBOl+TZih/wLAzBdBapclHEuCyGDC/EWXAK4aUKMN/R/p3aqm0Pd6obtLTBUBIEs xWeF3Gb5RUsNiKJ6Ua/LY2rOKjgg7hhMe49b2aEuWTiZF7wYTLlA+jBBPuQIj/AW0xqC yZe3Fd+el5ruJ2sjxMJr4pWntv7b/RL5W/KemIs/h2QjWL/3+1zs/Uw+F4MylOevxmiw Dnuw==
X-Gm-Message-State: ALoCoQndTLqNFuDsZjbGsZ9rFQC+Fqpuvq6oY5/6lzrPRJKxJlpACrjLaWCXnOVjllUBQuVEtoY93Za0XIR8um7ScetHNoO+mXkoFhMAu7d/9SJdHBSz9EY=
X-Received: by 10.66.192.7 with SMTP id hc7mr89267523pac.48.1451428081680; Tue, 29 Dec 2015 14:28:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.156.165 with HTTP; Tue, 29 Dec 2015 14:27:42 -0800 (PST)
From: Michael Bradshaw <mjbshaw@google.com>
Date: Tue, 29 Dec 2015 14:27:42 -0800
Message-ID: <CAHUoETLC4dQQ7=TOuTXZ3aDjKCCJgz2s-8Gb33MoSAP3hgRQiQ@mail.gmail.com>
To: cellar@ietf.org
Content-Type: multipart/alternative; boundary="047d7bdcac443a1580052810ef65"
Archived-At: <http://mailarchive.ietf.org/arch/msg/cellar/ncwG7Iaqrj0wr9Piqw3xM8MjKD8>
Subject: [Cellar] On the multiplicity of Info elements
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Dec 2015 22:28:03 -0000

Info elements may be repeated within a Segment since it is marked as "mult."

Is this correct, and does it make sense? It seems to me like there should
be one Info element within a Segment. I'm actually not really sure how to
sanely handle two Info elements within the same Segment.

--Michael

v2.23.0 | Report a Bug | By Email