Re: [stir] DRAFT STIR Agenda for London

Christer Holmberg <> Wed, 14 March 2018 08:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1BFE7126C0F for <>; Wed, 14 Mar 2018 01:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bXnpAYQ1ZRP5 for <>; Wed, 14 Mar 2018 01:39:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BA84912783A for <>; Wed, 14 Mar 2018 01:39:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256;; s=mailgw201801; c=relaxed/simple; q=dns/txt;; t=1521016755; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=DAwP97CF5MuYn5XQ53cgI3vPUx9vKQPIZ7Gj+ZO+EhQ=; b=BOx6rKz+X4UbtHUNJXJmV3y52UWmxBbyNZKtrEHK1eckhBDIDh/kaSggQDE+NA0K Ls3QkOisYXk6TLwLslEBPx98eRiPUFoZ1kC78PzASt0rOJVZf0W5lR9JfsvBjlJd CJlNExKyQWkzDl46fsmDXl6QT8d8Y1rltMlspo/60U8=;
X-AuditID: c1b4fb25-669ff70000006222-3f-5aa8dfb3e990
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 7B.76.25122.3BFD8AA5; Wed, 14 Mar 2018 09:39:15 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0382.000; Wed, 14 Mar 2018 09:39:15 +0100
From: Christer Holmberg <>
To: "Gorman, Pierce A [CTO]" <>, Russ Housley <>, IETF STIR Mail List <>
Thread-Topic: [stir] DRAFT STIR Agenda for London
Thread-Index: AQHTt+0fEDwMiDqclkW7s196x6oZNKPJe1iggAMUKACAAvFSAA==
Date: Wed, 14 Mar 2018 08:39:14 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7pe7m+yuiDPa2G1q8enGT3eLEt/+M FsvXbmNyYPZYsuQnk0fbpd3MHqvufGENYI7isklJzcksSy3St0vgyri0JqFgmWLFysOT2BsY D0t1MXJwSAiYSHx+wt/FyMUhJHCYUWLhtNfsEM4SRokJm98ygxSxCVhIdP/TBomLCDQzSry9 tpK1i5GTQ1jAQGLltelsILaIgKHEwbmboWwnie6fj1hAbBYBVYlf+9+C1fMKWEtc6NvFBrHg IKPExxtLmEASnAIeEr+X/WQGsRkFxCS+n1oDFmcWEJe49WQ+mC0hICCxZM95ZghbVOLl439g Q0UF9CQ2nLjNDhFXlLg6fTlUr57EjalT2CBsa4nVSx4zQ9jaEssWvmaGOEhQ4uTMJywTGMVm IVk3C0n7LCTts5C0z0LSvoCRdRWjaHFqcVJuupGxXmpRZnJxcX6eXl5qySZGYKwd3PJbdQfj 5TeOhxgFOBiVeHgXXlgRJcSaWFZcmXuIUYKDWUmEd6sMUIg3JbGyKrUoP76oNCe1+BCjNAeL kjjvHOH2KCGB9MSS1OzU1ILUIpgsEwenVANj/QrmoDVGC0zU3Qu4Zv6v1Gh0/jw9YY/SlQVP d831/T/5r/Fzt3cMsj3dtwo05nQynpDpO2V5YEcjB49VuL/TrZbNk+9udBKbMfdIguzerDvL A3v2Bd6bsKSa9cOTqHS2+3H7jK/ZMr35onqpTdQ+9Jh9YNiRxuWMM/WY9NO9YwvPNYS0NYQp sRRnJBpqMRcVJwIA5eyb8bECAAA=
Archived-At: <>
Subject: Re: [stir] DRAFT STIR Agenda for London
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 14 Mar 2018 08:39:55 -0000


For the Feature-Caps header field, we have the following text in RFC 6809:

   "When a SIP entity adds a Feature-Caps header field to a SIP message,
    it MUST place the header field before any existing Feature-Caps
    header field in the message to be forwarded, so that the added header
    field becomes the top-most one.²

If we were to take the same approach for Identity, the text could look
something like:

   "When a SIP entity adds an Identity header field to a SIP request,
    it MUST place the header field before any existing Identity
    header field in the message to be forwarded, so that the added header
    field becomes the top-most one.²

Alternatively, we could say that a header field is places AFTER any
existing header field. As long as we say something :)

And, if we decide that the order of header fields has no relevance, we
should say that. However, I would at least not suggest such approach.



On 12/03/18 15:43, "Gorman, Pierce A [CTO]" <>;

>I agree that the question of order (or not) of Identity headers needs to
>be resolved.
>I started to write assumptions and questions on this topic but decided it
>wouldn't add much to a discussion amongst development professionals who
>have encountered the issue before (which is my assumption about the
>authors and Christer).  I can re-create it if anyone wants it.
>-----Original Message-----
>From: Christer Holmberg []
>Sent: Saturday, March 10, 2018 11:33 AM
>To: Russ Housley <>;; IETF STIR Mail List
>Subject: Re: [stir] DRAFT STIR Agenda for London
>I think there are some generic things that we need to sort out.
>For example, do we specify in which order Identity header fields are
>added to a SIP message. Or, do we assume they can be put in any order,
>possible re-ordered by intermediaries, and the entities consuming them
>will figure out how they are related?
>I think that is an essential issue to solve, considering that there are a
>number of PASSporT extensions in the pipeline. And, we should make a
>decision that apply to all of them.
>-----Original Message-----
>From: stir [] On Behalf Of Russ Housley
>Sent: 09 March 2018 23:25
>To: IETF STIR Mail List <>;
>Subject: [stir] DRAFT STIR Agenda for London
>We only have 1 hour.  We received more speaking slots than we expected.
>I have ordered the speaking slots to put priority on the active WG
>documents.  Time will be VERY tight.
>For the active WG documents, please focus on the changes since Singapore
>and open issues.
>For the other documents, please introduce the high-level concept, and
>then as the WG for advice on the way forward.
>= = = = = = = = =
>STIR WG Agenda for IETF 101
>Thursday, 22 March 2018 at 11:00 AM
>Co-chairs: Robert Sparks and Russ Housley
>0)  Minute Taker, Jabber Scribe, Bluesheets
>1)  Agenda Bash
>2)  Documents that have been sent to the IESG
>    a) 5 min : draft-ietf-stir-rph-03 (Ray, Martin, Subir, and An)
>3)  Active Working Group Documents
>    a) 10 min : draft-ietf-stir-passport-shaken-01 (Chris and Mary)
>    b) 10 min : draft-ietf-stir-passport-divert-02 (Jon)
>    c) 10 min : draft-ietf-stir-oob-02 (EKR and Jon)
>4)  Other Business (if time allows)
>    a) 5 min : draft-burger-stir-iana-cert-00 (Eric)
>    b) 5 min : draft-peterson-stir-rfc4916-update-00 (Jon and Chris)
>    c) 5 min : draft-rosenberg-stir-callback-00 (Jonathan and Cullen)
>    d) 5 min : draft-rosenberg-stir-sipcoin-00 (Jonathan and Cullen)
>5)  Wrap Up
>stir mailing list
>This e-mail may contain Sprint proprietary information intended for the
>sole use of the recipient(s). Any use by others is prohibited. If you are
>not the intended recipient, please contact the sender and delete all
>copies of the message.