[Tls-reg-review] [IANA #1238927] FW: IANA TLS ALPN registry for SIP

Sabrina Tanamal via RT <iana-prot-param@iana.org> Tue, 30 August 2022 18:36 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2513C157B49 for <tls-reg-review@ietfa.amsl.com>; Tue, 30 Aug 2022 11:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bgkgzq15MPOE for <tls-reg-review@ietfa.amsl.com>; Tue, 30 Aug 2022 11:36:06 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (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 EF5DBC157908 for <tls-reg-review@ietf.org>; Tue, 30 Aug 2022 11:36:05 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id D82B9F8534; Tue, 30 Aug 2022 18:36:04 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id D2D49210EA; Tue, 30 Aug 2022 18:36:04 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: Sabrina Tanamal via RT <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <rt-4.4.3-6822-1661584852-984.1238927-37-0@icann.org>
References: <RT-Ticket-1238927@icann.org> <14F42417-364C-47CE-8943-6BEFD902906F@edvina.net> <B7D2D6F9-34F8-4188-A7BF-EC9DFF23F018@edvina.net> <39F0E7D4-1560-4CA3-865F-86D6ECBADEA9@akamai.com> <BCA39EF8-067E-472D-99A5-941071E356D8@akamai.com> <6D438DC1-62CD-447A-85D0-6A9EDC9D993C@akamai.com> <rt-4.4.3-4024-1661528909-49.1238927-9-0@icann.org> <1F4B8EAD-51A7-4761-9D4F-BA0CCA180A1B@akamai.com> <EF8A767B-4C03-4DEF-85D6-81478EE9FB8A@edvina.net> <rt-4.4.3-6822-1661584852-984.1238927-37-0@icann.org>
Message-ID: <rt-4.4.3-15173-1661884564-99.1238927-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1238927
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
To: oej@edvina.net
CC: tls-reg-review@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 30 Aug 2022 18:36:04 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/1X_ofBAEhL4TwsYwc4nk5HLXVfU>
Subject: [Tls-reg-review] [IANA #1238927] FW: IANA TLS ALPN registry for SIP
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.39
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2022 18:36:09 -0000

Hi Olle, 

We've added the following entry to the TLS ALPN Protocol IDs registry: 

Protocol: SIP
Identification Sequence: 0x73 0x69 0x70 0x2f 0x32 ("sip/2")
Reference: [RFC3261]

Please see
https://www.iana.org/assignments/tls-extensiontype-values

Best regards, 

Sabrina Tanamal
Lead IANA Services Specialist

On Sat Aug 27 07:20:52 2022, oej@edvina.net wrote:
> 
> 
> > On 27 Aug 2022, at 00:02, Salz, Rich <rsalz@akamai.com> wrote:
> >
> > Ole, this is for you to answer.
> >
> > Approved either way by me.
> >
> > On 8/26/22, 11:48 AM, "Sabrina Tanamal via RT" <iana-prot-param-
> > comment@iana.org> wrote:
> >
> > Hi Rich, all,
> >
> > Thanks for forwarding this request. We have a quick question before
> > we make this registration.
> >
> > For the Identification Sequence field, we see " 0x73 0x69 0x70
> > (“sip")" listed below, but Section 2 of draft-johansson-sip-alpn
> > says, "Identification Sequence: 0x73 0x69 0x70 0x2f 0x32 ("sip/2")",
> > which sequence should we list in the registry?
> sip/2
> 
> Thanks,
> /O
> >
> > Thanks and best regards,
> >
> > Sabrina Tanamal
> >  Lead IANA Services Specialist
> >
> > On Fri Aug 26 14:45:59 2022, rsalz@akamai.com wrote:
> >>
> >>
> >> From: Rich Salz <rsalz@akamai.com>
> >> Date: Friday, August 26, 2022 at 10:42 AM
> >> To: Olle Johansson <oej@edvina.net>
> >> Cc: Yoav Nir <ynir.ietf@gmail.com>, "Salz, Rich"
> >> <rsalz=40akamai.com@dmarc.ietf.org>, "tls-reg-review@ietf.org" <tls-
> >> reg-review@ietf.org>
> >> Subject: Re: [Tls-reg-review] IANA TLS ALPN registry for SIP
> >>
> >> IANA makes an update.  They’re on this tls-reg-review list.
> >>
> >> From: Olle Johansson <oej@edvina.net>
> >> Date: Friday, August 26, 2022 at 9:53 AM
> >> To: Rich Salz <rsalz@akamai.com>
> >> Cc: Yoav Nir <ynir.ietf@gmail.com>, "Salz, Rich"
> >> <rsalz=40akamai.com@dmarc.ietf.org>, "tls-reg-review@ietf.org" <tls-
> >> reg-review@ietf.org>
> >> Subject: Re: [Tls-reg-review] IANA TLS ALPN registry for SIP
> >>
> >> Thank you gentlemen.
> >>
> >> What’s the next step for getting an actual update in the registry?
> >>
> >> /O
> >>
> >> On 26 Aug 2022, at 15:45, Salz, Rich
> >> <rsalz@akamai.com<mailto:rsalz@akamai.com>> wrote:
> >>
> >> I also approve.
> >>
> >> From: Yoav Nir <ynir.ietf@gmail.com<mailto:ynir.ietf@gmail.com>>
> >> Date: Friday, August 26, 2022 at 3:34 AM
> >> To: "Salz, Rich"
> >> <rsalz=40akamai.com@dmarc.ietf.org<mailto:rsalz=40akamai.com@dmarc.ietf.org>>
> >> Cc: Olle Johansson <oej@edvina.net<mailto:oej@edvina.net>>, "tls-
> >> reg-
> >> review@ietf.org<mailto:tls-reg-review@ietf.org>" <tls-reg-
> >> review@ietf.org<mailto:tls-reg-review@ietf.org>>
> >> Subject: Re: [Tls-reg-review] IANA TLS ALPN registry for SIP
> >>
> >> I think it’s this one, no?
> >>   https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-
> >> johansson-sip-
> >> __;!!GjvTz_vk!RWEUcBXs2MQVvE9YYiedQhmQt8W1cjSAwi2nGquXup0mn0l_v7FmwRwoszoDTUYCxOH-
> >> gewd_AvYt51Wg1TfmoQ$
> >> alpn<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-
> >> johansson-sip-alpn__;!!GjvTz_vk!S2oieA3YUt-D2-nfZqMgSmZ1AJKOfZCAZb-
> >> u4gPID5FW-a4s2-shFScHR2r5pBZ3VIUj_uc0O5MmQz0$>
> >>
> >> In any case, this seems straightforward, so I guess I approve.
> >> Rich?
> >>
> >>
> >>
> >> On 25 Aug 2022, at 18:41, Salz, Rich
> >> <rsalz=40akamai.com@dmarc.ietf.org<mailto:rsalz=40akamai.com@dmarc.ietf.org>>
> >> wrote:
> >>
> >> I am sorry things slipped through the cracks.  I’m guessing nobody
> >> noticed that you did actually write a draft.
> >>
> >> An expired draft is fine. What’s the link?
> >>
> >>
> >> From: Olle Johansson <oej@edvina.net<mailto:oej@edvina.net>>
> >> Date: Thursday, August 25, 2022 at 3:27 AM
> >> To: "tls-reg-review@ietf.org<mailto:tls-reg-review@ietf.org>" <tls-
> >> reg-review@ietf.org<mailto:tls-reg-review@ietf.org>>
> >> Subject: [Tls-reg-review] Fwd: IANA TLS ALPN registry for SIP
> >>
> >> Just for reference, here’s the first mail in this thread.
> >>
> >> /O
> >>
> >>
> >>
> >> Begin forwarded message:
> >>
> >> From: "Olle E. Johansson" <oej@edvina.net<mailto:oej@edvina.net>>
> >> Subject: IANA TLS ALPN registry for SIP
> >> Date: 30 April 2021 at 09:12:28 CEST
> >> To: tls-reg-review@ietf.org<mailto:tls-reg-review@ietf.org>
> >>
> >> I would like to register a TLS ALPN registry entry for the Session
> >> Initiation Protocol according to the following entry:
> >>
> >> Protocol:  SIP
> >> Identification Sequence:
> >>   0x73 0x69 0x70  (“sip")
> >> Reference:  [RFC3261]
> >>
> >> Best regards,
> >> /Olle E. Johansson
> >>
> >> _______________________________________________
> >> tls-reg-review mailing list
> >> tls-reg-review@ietf.org<mailto:tls-reg-review@ietf.org>
> >>   https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls-
> >> reg-
> >> __;!!GjvTz_vk!RWEUcBXs2MQVvE9YYiedQhmQt8W1cjSAwi2nGquXup0mn0l_v7FmwRwoszoDTUYCxOH-
> >> gewd_AvYt51W3cnjKLs$
> >> review<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/tls-
> >> reg-review__;!!GjvTz_vk!S2oieA3YUt-D2-nfZqMgSmZ1AJKOfZCAZb-
> >> u4gPID5FW-
> >> a4s2-shFScHR2r5pBZ3VIUj_uc0lAjTu60$>
> >>
> >
> > _______________________________________________
> > tls-reg-review mailing list
> > tls-reg-review@ietf.org
> >   https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls-
> > reg-
> > review__;!!GjvTz_vk!RWEUcBXs2MQVvE9YYiedQhmQt8W1cjSAwi2nGquXup0mn0l_v7FmwRwoszoDTUYCxOH-
> > gewd_AvYt51WVTpjKGQ$
> >