[stir] draft-ietf-stir-rfc4474bis-16: Syntax question

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 03 January 2018 18:57 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6334E126FB3 for <stir@ietfa.amsl.com>; Wed, 3 Jan 2018 10:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=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 xddAix1g-hQ7 for <stir@ietfa.amsl.com>; Wed, 3 Jan 2018 10:57:48 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D32A1126DEE for <stir@ietf.org>; Wed, 3 Jan 2018 10:57:46 -0800 (PST)
X-AuditID: c1b4fb2d-b4dff70000007932-99-5a4d27a80d26
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 5D.94.31026.8A72D4A5; Wed, 3 Jan 2018 19:57:45 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0352.000; Wed, 3 Jan 2018 19:57:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: IETF STIR Mail List <stir@ietf.org>
Thread-Topic: draft-ietf-stir-rfc4474bis-16: Syntax question
Thread-Index: AdOEw5NeB+uYQibOTjeCuIYC3y7mnw==
Date: Wed, 03 Jan 2018 18:57:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C0E903C@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B6C0E903CESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyM2K7uu5Kdd8og/PTmS2Wr93G5MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujJYNkxkLLhlUNL69zNzAeFuri5GTQ0LARKL7Sy97FyMXh5DA YUaJ87NPsoAkhAQWM0r8a9DpYuTgYBOwkOj+pw0SFhFQl2ht62MGsYUFzCVaTm1ihYjbSNz8 vIwdwtaTeLZtEVicRUBFovXYIWaQMbwCvhIPGqNBwowCYhLfT61hArGZBcQlbj2ZzwRxjoDE kj3nmSFsUYmXj/+xQthKEmsPb2eBqM+XeDX9G9gqXgFBiZMzn7BMYBSchWTULCRls5CUQcR1 JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWMosWpxcW56UbGeqlFmcnFxfl5enmpJZsYgWF/ cMtv3R2Mq187HmIU4GBU4uG9LeMbJcSaWFZcmXuIUYKDWUmE1y3LJ0qINyWxsiq1KD++qDQn tfgQozQHi5I470lP3ighgfTEktTs1NSC1CKYLBMHp1QDo8X8nZ4Lj/PqlRTItx88b8g5MXmf bJZGUcTpBq+F21nf/Gn4cSWu+O08SRF2j079uLYEpzizeWEnTuQtWn351ocVJzeoiZx4YKvW r7O/66PSZKEr63NkC21b/z6s9F318vkHXsk0uU0i+cvmHeDYr6z4M92Py4cl/23aPNGzf37k zr+/QFCiSYmlOCPRUIu5qDgRAD+FoU93AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/nrZT-kAGT2UkMy4Z-9LuEqyZcn8>
Subject: [stir] draft-ietf-stir-rfc4474bis-16: Syntax question
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2018 18:57:50 -0000

Hi,

Section 4 says:

   "Note that unlike the prior specification
   in RFC4474, the Identity header field is now allowed to appear more
   than one time in a SIP request.  The revised grammar for the Identity
   header field builds on the ABNF [RFC5234] in RFC 3261 [RFC3261]
   Section 25.  It is as follows:

      Identity = "Identity" HCOLON signed-identity-digest SEMI
      ident-info *( SEMI ident-info-params )
      ..."

However, that syntax does NOT allow multiple Identity header fields, according to the rules in RFC 3261:

   "Multiple header field rows with the same field-name MAY be present in
   a message if and only if the entire field-value for that header field
   is defined as a comma-separated list"

It should be something like:

     Identity = "Identity" HCOLON signed-identity * (COMMA signed-identity)
     signed-identity = signed-identity-digest SEMI identi-info * (SEMI ident-info-params)
     ..."

Or, misunderstood I have?

Regards,

Christer