
From nobody Mon Apr  1 10:42:04 2019
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0761D120187 for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 10:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level: 
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 E5GchjsEXX4x for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 10:42:00 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 3B352120075 for <sipcore@ietf.org>; Mon,  1 Apr 2019 10:42:00 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x31HflvG007808 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Apr 2019 12:41:48 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1554140510; bh=IOVTF8SSYuOS19qhphIN+EcG291UDlM/cGP33Zgi05c=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=pRxxF92Wzn7BAS+P52UqK6J6G2zuoaFMV/3TKWRXbR7OUEx091IndHpm+L/lM08WQ A1a3mGH3+9gZNu15uClz7S4R7jPAyPum3t0hTvf9qMGIyI+IsAv7/eT53/NeYbKnV+ CrQ9acwMBAFN93uet3vpCZxA7n9pPFwjtaWqOI0U=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be mutabilis-2.local
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "rifaat.sy@gmail.com" <rifaat.sy@gmail.com>, "Dale R. Worley" <worley@ariadne.com>, SIPCORE <sipcore@ietf.org>, Andy Hutton <andyhutton.ietf@gmail.com>
References: <D6AB3EE7.2B2C4%christer.holmberg@ericsson.com> <87vaexg01a.fsf@hobgoblin.ariadne.com> <CAB7PXwSQ7dhWTYsrevpttcrUfWftbJ4Hc_XJmbKMua4eeT_Z_Q@mail.gmail.com> <E4EAAECD-AE0C-4D7B-9DC8-67993F010808@ericsson.com> <CAGL6epK96StrqLxc4yfQ1Y3ENysH=+ME2SqrP0qbGB6njbgJoA@mail.gmail.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <b64ba0e6-164b-c790-980a-fb1b54ead437@nostrum.com>
Date: Mon, 1 Apr 2019 12:41:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.0
MIME-Version: 1.0
In-Reply-To: <CAGL6epK96StrqLxc4yfQ1Y3ENysH=+ME2SqrP0qbGB6njbgJoA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/kn2eTnvFGZ80w25Effsm5yvcJHc>
Subject: Re: [sipcore] ABNF: request-digest: 32 characters, only 32 characters and nothing but 32 characters?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 17:42:02 -0000

Hi Rifaat,

On 3/30/19 8:28 PM, Rifaat Shekh-Yusef wrote:
> I am honestly really puzzled why this draft has not be adopted long time 
> ago.
> This could have been delivered few years ago already.
> 
> What is stopping this from happening?


Good question. Digging through the SIPCORE mailing list, this co-chair 
found a plan to call for WG adoption for 
draft-yusef-sipcore-digest-scheme after a few other drafts made it 
through WGLC. Given that those drafts are in the RFC editor's queue, I 
don't think anything stopped the call for adoption except that maybe it 
fell off the chairs' to-do list.

Please update the draft (it has expired), and I will send a separate 
email to the list about WG adoption.

Thanks!

Jean

PS - If you think the chairs may have forgotten something, feel free to 
send a note to the list or the sipcore-chairs email address. Thx!




> 
> Regards,
>   Rifaat
> 
> 
> 
> On Fri, Mar 29, 2019 at 4:47 AM Christer Holmberg 
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> 
> wrote:
> 
>     Hi,
> 
>     This thread is a year old, but I would like to bring it back to the
>     surface..
> 
>     The syntax needs to be fixed, so I would like the WG to adopt the draft.
> 
>     Regards,
> 
>     Christer
> 
> 
>     ﻿On 21/03/2018, 19.54, "Andy Hutton" <andyhutton.ietf@gmail.com
>     <mailto:andyhutton.ietf@gmail.com>> wrote:
> 
>          I would also like to see draft-yusef-sipcore-digest-scheme adopted.
> 
>          Andy
> 
>          On 16 February 2018 at 02:07, Dale R. Worley
>     <worley@ariadne.com <mailto:worley@ariadne.com>> wrote:
>          > Christer Holmberg <christer.holmberg@ericsson.com
>     <mailto:christer.holmberg@ericsson.com>> writes:
>          >> I realised that Rifaat's draft actually updates the ABNF (by
>     removing the
>          >> 32 characters restriction), so we wouldn't need anything in
>     addition to
>          >> that.
>          >
>          > I was going to say, What is the name of the draft?, but it's
>          > draft-yusef-sipcore-digest-scheme, which is dated last
>     September, which
>          > is probably why I remember it.
>          >
>          > It not only updates the ABNF in RFC 3261, it also connects it
>     with RFC
>          > 7611.
>          >
>          > ---> So, I call for adoption of
>     draft-yusef-sipcore-digest-scheme as a
>          > WG draft.
>          >
>          > Dale
>          >
>          > _______________________________________________
>          > sipcore mailing list
>          > sipcore@ietf.org <mailto:sipcore@ietf.org>
>          > https://www.ietf.org/mailman/listinfo/sipcore
> 
> 
>     _______________________________________________
>     sipcore mailing list
>     sipcore@ietf.org <mailto:sipcore@ietf.org>
>     https://www.ietf.org/mailman/listinfo/sipcore
> 
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 


From nobody Mon Apr  1 13:41:06 2019
Return-Path: <rifaat.ietf@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88431203B1 for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 13:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pXUWIibD-X3H for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 13:41:02 -0700 (PDT)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 63A0112004B for <sipcore@ietf.org>; Mon,  1 Apr 2019 13:41:02 -0700 (PDT)
Received: by mail-it1-x12f.google.com with SMTP id g17so1435113ita.2 for <sipcore@ietf.org>; Mon, 01 Apr 2019 13:41:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cCH6hFV2FoFDOjvkYuHj7KFVgJ39+ux58fxyhnAgLE0=; b=oIlGh6BrB1t03jID8CeBofqrsVtMVy1U7dLBNYguCahe4tjm9JomNpAc+VkUVuioxp Ou+cOvs1x5dF1UrFhDb+l4a8fv2BpHI4QykXryh8zb8Z941G9KPMhb3KD4fc13YloTrK zQsOLuQx//vRueAtkFSfEMmtnNvQA8x6GmPq1YWGiHYgA6g1uwMRtWT/cM9bL7uPaylH 6fO/Aqy/ziYNuE1cWVBj4kfxv+k9AInEX5S5VoQNa5MjN9ac3jeSGj3SPaSeAE6BCGZc ELrOyU+fQWHMUzT7ncdkAt8cnyORVB0UOnKZcW3rhrCj3ComU7+rP7x5rvoawaHqdvb5 zUOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cCH6hFV2FoFDOjvkYuHj7KFVgJ39+ux58fxyhnAgLE0=; b=og62vWpK3Zdyiou58wBU2sxBes80fkg8PSurhJ1L7pCE0uU7wJKliZn0jRnRj6p+CN af/XzZLNDgDhu2qUY1Vy85VcQIO81PKBo+vx0MVzel8Qn2YQlYn7IvtlMwuLlMlaoiiL sY2Tr9DxS4YbPe6GMCoBmV6OdaoLXgepb6wReIx3MNFJK7wq/Akhi/eKenk5iOUiJVqb WY/uj+I0L0PH9PQEipaCMw8fU8IomT8jmfkZkQXj0Qw4HWfXPlyS8G1y2LeGUT90Ugy9 f3dlu4d4xn1+vYCFYwkRsHQ2+5scBFmaIuxcBmAQnz+SyhcH/itkssYZ65uME1zKzd/m pjDg==
X-Gm-Message-State: APjAAAVdi1WJk2TCJfr2msM9jGsB+Yzu2jG0aLPHmibowqU98ovukioI EtbFZSiFRgIUo0z8W6j26MkBwGdGXxAnQuOyUrs=
X-Google-Smtp-Source: APXvYqxQ34iN7m32Nt2+Mm/DRT6Dr/6hEtU33JLCHWy6lIyo85j9pwHBvGgYn4Uqy71L6HgYRsOVLpOgMHlZmibACBM=
X-Received: by 2002:a24:e501:: with SMTP id g1mr1314595iti.22.1554151261426; Mon, 01 Apr 2019 13:41:01 -0700 (PDT)
MIME-Version: 1.0
References: <D6AB3EE7.2B2C4%christer.holmberg@ericsson.com> <87vaexg01a.fsf@hobgoblin.ariadne.com> <CAB7PXwSQ7dhWTYsrevpttcrUfWftbJ4Hc_XJmbKMua4eeT_Z_Q@mail.gmail.com> <E4EAAECD-AE0C-4D7B-9DC8-67993F010808@ericsson.com> <CAGL6epK96StrqLxc4yfQ1Y3ENysH=+ME2SqrP0qbGB6njbgJoA@mail.gmail.com> <b64ba0e6-164b-c790-980a-fb1b54ead437@nostrum.com>
In-Reply-To: <b64ba0e6-164b-c790-980a-fb1b54ead437@nostrum.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Mon, 1 Apr 2019 16:40:50 -0400
Message-ID: <CAGL6epL-khpu1juN4xE7gpwAB4B7g+AQydeoM22DzSUGF7sJgA@mail.gmail.com>
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>,  "rifaat.sy@gmail.com" <rifaat.sy@gmail.com>, "Dale R. Worley" <worley@ariadne.com>, SIPCORE <sipcore@ietf.org>,  Andy Hutton <andyhutton.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000dd56bd05857e0987"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/vuPENGUcoHBRRRu0mla1OuPEBCY>
Subject: Re: [sipcore] ABNF: request-digest: 32 characters, only 32 characters and nothing but 32 characters?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 20:41:05 -0000

--000000000000dd56bd05857e0987
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Jean!

I have just refreshed this document:
https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/

Regards,
 Rifaat


On Mon, Apr 1, 2019 at 1:41 PM A. Jean Mahoney <mahoney@nostrum.com> wrote:

> Hi Rifaat,
>
> On 3/30/19 8:28 PM, Rifaat Shekh-Yusef wrote:
> > I am honestly really puzzled why this draft has not be adopted long tim=
e
> > ago.
> > This could have been delivered few years ago already.
> >
> > What is stopping this from happening?
>
>
> Good question. Digging through the SIPCORE mailing list, this co-chair
> found a plan to call for WG adoption for
> draft-yusef-sipcore-digest-scheme after a few other drafts made it
> through WGLC. Given that those drafts are in the RFC editor's queue, I
> don't think anything stopped the call for adoption except that maybe it
> fell off the chairs' to-do list.
>
> Please update the draft (it has expired), and I will send a separate
> email to the list about WG adoption.
>
> Thanks!
>
> Jean
>
> PS - If you think the chairs may have forgotten something, feel free to
> send a note to the list or the sipcore-chairs email address. Thx!
>
>
>
>
> >
> > Regards,
> >   Rifaat
> >
> >
> >
> > On Fri, Mar 29, 2019 at 4:47 AM Christer Holmberg
> > <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>=
>
>
> > wrote:
> >
> >     Hi,
> >
> >     This thread is a year old, but I would like to bring it back to the
> >     surface..
> >
> >     The syntax needs to be fixed, so I would like the WG to adopt the
> draft.
> >
> >     Regards,
> >
> >     Christer
> >
> >
> >     =EF=BB=BFOn 21/03/2018, 19.54, "Andy Hutton" <andyhutton.ietf@gmail=
.com
> >     <mailto:andyhutton.ietf@gmail.com>> wrote:
> >
> >          I would also like to see draft-yusef-sipcore-digest-scheme
> adopted.
> >
> >          Andy
> >
> >          On 16 February 2018 at 02:07, Dale R. Worley
> >     <worley@ariadne.com <mailto:worley@ariadne.com>> wrote:
> >          > Christer Holmberg <christer.holmberg@ericsson.com
> >     <mailto:christer.holmberg@ericsson.com>> writes:
> >          >> I realised that Rifaat's draft actually updates the ABNF (b=
y
> >     removing the
> >          >> 32 characters restriction), so we wouldn't need anything in
> >     addition to
> >          >> that.
> >          >
> >          > I was going to say, What is the name of the draft?, but it's
> >          > draft-yusef-sipcore-digest-scheme, which is dated last
> >     September, which
> >          > is probably why I remember it.
> >          >
> >          > It not only updates the ABNF in RFC 3261, it also connects i=
t
> >     with RFC
> >          > 7611.
> >          >
> >          > ---> So, I call for adoption of
> >     draft-yusef-sipcore-digest-scheme as a
> >          > WG draft.
> >          >
> >          > Dale
> >          >
> >          > _______________________________________________
> >          > sipcore mailing list
> >          > sipcore@ietf.org <mailto:sipcore@ietf.org>
> >          > https://www.ietf.org/mailman/listinfo/sipcore
> >
> >
> >     _______________________________________________
> >     sipcore mailing list
> >     sipcore@ietf.org <mailto:sipcore@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/sipcore
> >
> >
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
> >
>

--000000000000dd56bd05857e0987
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Thanks Jean!<div><br></div><div>I have ju=
st refreshed this document:</div><div><a href=3D"https://datatracker.ietf.o=
rg/doc/draft-yusef-sipcore-digest-scheme/">https://datatracker.ietf.org/doc=
/draft-yusef-sipcore-digest-scheme/</a><br></div><div><br></div><div>Regard=
s,</div><div>=C2=A0Rifaat</div><div><br></div></div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 1, 2019 at =
1:41 PM A. Jean Mahoney &lt;<a href=3D"mailto:mahoney@nostrum.com">mahoney@=
nostrum.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Hi Rifaat,<br>
<br>
On 3/30/19 8:28 PM, Rifaat Shekh-Yusef wrote:<br>
&gt; I am honestly really puzzled why this draft has not be adopted long ti=
me <br>
&gt; ago.<br>
&gt; This could have been delivered few years=C2=A0ago already.<br>
&gt; <br>
&gt; What is stopping this from happening?<br>
<br>
<br>
Good question. Digging through the SIPCORE mailing list, this co-chair <br>
found a plan to call for WG adoption for <br>
draft-yusef-sipcore-digest-scheme after a few other drafts made it <br>
through WGLC. Given that those drafts are in the RFC editor&#39;s queue, I =
<br>
don&#39;t think anything stopped the call for adoption except that maybe it=
 <br>
fell off the chairs&#39; to-do list.<br>
<br>
Please update the draft (it has expired), and I will send a separate <br>
email to the list about WG adoption.<br>
<br>
Thanks!<br>
<br>
Jean<br>
<br>
PS - If you think the chairs may have forgotten something, feel free to <br=
>
send a note to the list or the sipcore-chairs email address. Thx!<br>
<br>
<br>
<br>
<br>
&gt; <br>
&gt; Regards,<br>
&gt;=C2=A0 =C2=A0Rifaat<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On Fri, Mar 29, 2019 at 4:47 AM Christer Holmberg <br>
&gt; &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank=
">christer.holmberg@ericsson.com</a> &lt;mailto:<a href=3D"mailto:christer.=
holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>=
&gt;&gt; <br>
&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Hi,<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0This thread is a year old, but I would like to brin=
g it back to the<br>
&gt;=C2=A0 =C2=A0 =C2=A0surface..<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0The syntax needs to be fixed, so I would like the W=
G to adopt the draft.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Regards,<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Christer<br>
&gt; <br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0=EF=BB=BFOn 21/03/2018, 19.54, &quot;Andy Hutton&qu=
ot; &lt;<a href=3D"mailto:andyhutton.ietf@gmail.com" target=3D"_blank">andy=
hutton.ietf@gmail.com</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D"mailto:andyhutton.ietf@gmail.=
com" target=3D"_blank">andyhutton.ietf@gmail.com</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I would also like to see draft-yusef=
-sipcore-digest-scheme adopted.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Andy<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 On 16 February 2018 at 02:07, Dale R=
. Worley<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"mailto:worley@ariadne.com" target=3D=
"_blank">worley@ariadne.com</a> &lt;mailto:<a href=3D"mailto:worley@ariadne=
.com" target=3D"_blank">worley@ariadne.com</a>&gt;&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.com</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D"mailto:christer.holmberg@eric=
sson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;&gt; writ=
es:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; I realised that Rifaat&#39;=
s draft actually updates the ABNF (by<br>
&gt;=C2=A0 =C2=A0 =C2=A0removing the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; 32 characters restriction),=
 so we wouldn&#39;t need anything in<br>
&gt;=C2=A0 =C2=A0 =C2=A0addition to<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; that.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; I was going to say, What is the=
 name of the draft?, but it&#39;s<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; draft-yusef-sipcore-digest-sche=
me, which is dated last<br>
&gt;=C2=A0 =C2=A0 =C2=A0September, which<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; is probably why I remember it.<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; It not only updates the ABNF in=
 RFC 3261, it also connects it<br>
&gt;=C2=A0 =C2=A0 =C2=A0with RFC<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; 7611.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; ---&gt; So, I call for adoption=
 of<br>
&gt;=C2=A0 =C2=A0 =C2=A0draft-yusef-sipcore-digest-scheme as a<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; WG draft.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Dale<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; _______________________________=
________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; sipcore mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; <a href=3D"mailto:sipcore@ietf.=
org" target=3D"_blank">sipcore@ietf.org</a> &lt;mailto:<a href=3D"mailto:si=
pcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; <a href=3D"https://www.ietf.org=
/mailman/listinfo/sipcore" rel=3D"noreferrer" target=3D"_blank">https://www=
.ietf.org/mailman/listinfo/sipcore</a><br>
&gt; <br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0_______________________________________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0sipcore mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:sipcore@ietf.org" target=3D"_blan=
k">sipcore@ietf.org</a> &lt;mailto:<a href=3D"mailto:sipcore@ietf.org" targ=
et=3D"_blank">sipcore@ietf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/si=
pcore" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/li=
stinfo/sipcore</a><br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; sipcore mailing list<br>
&gt; <a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore</a><=
br>
&gt; <br>
</blockquote></div>

--000000000000dd56bd05857e0987--


From nobody Mon Apr  1 13:45:49 2019
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3EBB1201EB for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 13:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 09VsqN9O6rBk for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 13:45:45 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 0D4B01201B1 for <sipcore@ietf.org>; Mon,  1 Apr 2019 13:45:45 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x31KjhMK038346 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <sipcore@ietf.org>; Mon, 1 Apr 2019 15:45:44 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1554151544; bh=3q1o0XjK8UI3vKedsr6CCsvxVY5r+UJ9VGD0u/lm0YI=; h=To:From:Subject:Date; b=njaum2+yMrdPHfH/0Vw43dCh9Pseq2MMqfWocBbDx4xc6VX52xU00ubSrbVYAsI02 lJ0yCpDkx52ZkTvKkiqoMBDIwoJsfvn86hoGB23EM1nwDOPMepy0DTUaVXb24Z0FZF zl47uK91bpi6En6PCZtV3zuCdD2SkRvGDBkAWOKc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be mutabilis-2.local
To: SIPCORE <sipcore@ietf.org>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com>
Date: Mon, 1 Apr 2019 15:45:43 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/SnsR1CidKhNkX54czscoYgNxw3Q>
Subject: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 20:45:47 -0000

Hi all,

This is a call for adoption of draft-yusef-sipcore-digest-scheme in the 
SIPCORE working group.

https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/

Please send your comments to the list or to the chairs by April 15th.

Thanks!

Jean


From nobody Mon Apr  1 23:35:54 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29592120106 for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 23:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 WBKdXVVvKc8y for <sipcore@ietfa.amsl.com>; Mon,  1 Apr 2019 23:35:50 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-am5eur03on0617.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe08::617]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9FFE12001E for <sipcore@ietf.org>; Mon,  1 Apr 2019 23:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7YIZFVNYRV8TJVafsdKEeGuHfLIzoUQDi/Tn/apavg8=; b=AzuQFW9lNu4auSz34G5J/5fqjjjnZTBb0+phhdqNcMcy85GvN5pjNEhy4Y+3el6Fw7SX8tdp8E2HICPIpqZ8IhPABeGKRN6fd9VGXPsPv0bNCa8IQ+5deE3UXgFjQWEI+srDQeWTV0cF90YDm08R7iq8kPegIZbNH/GrwkNN+4U=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB4236.eurprd07.prod.outlook.com (20.176.166.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.8; Tue, 2 Apr 2019 06:35:47 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9%5]) with mapi id 15.20.1771.007; Tue, 2 Apr 2019 06:35:47 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "A. Jean Mahoney" <mahoney@nostrum.com>, SIPCORE <sipcore@ietf.org>
Thread-Topic: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
Thread-Index: AQHU6Mvzp9wdq8jKvUm6QzfaBlSBzqYonUqA
Date: Tue, 2 Apr 2019 06:35:47 +0000
Message-ID: <F6F9524E-B17C-47DC-8C6D-B7A87FDFF007@ericsson.com>
References: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com>
In-Reply-To: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ed4cae6f-a949-4099-d91e-08d6b73570bc
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR07MB4236; 
x-ms-traffictypediagnostic: HE1PR07MB4236:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <HE1PR07MB4236A3CEB2989DEA721BC04D93560@HE1PR07MB4236.eurprd07.prod.outlook.com>
x-forefront-prvs: 0995196AA2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(39860400002)(136003)(376002)(346002)(199004)(189003)(18543002)(53754006)(316002)(105586002)(2906002)(36756003)(7736002)(6116002)(97736004)(5660300002)(6246003)(478600001)(25786009)(33656002)(3846002)(44832011)(106356001)(8936002)(6512007)(966005)(53936002)(6306002)(81156014)(81166006)(8676002)(68736007)(71200400001)(2616005)(476003)(446003)(83716004)(6506007)(71190400001)(11346002)(4744005)(26005)(186003)(82746002)(486006)(256004)(76176011)(102836004)(66066001)(6436002)(86362001)(58126008)(110136005)(229853002)(6486002)(305945005)(14454004)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4236; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: NrxSbTTOkm8U0cnQZyrbg1iZsCZWz9ImJ6KBwhh79nAykF4nhhraKpEgazUpkzxl21r/d0dZflz8FDB5J3sPh8wumD0dZXDsnmm0E7soR4U8asEd5+TybDXltj7mSNYCKqhPz/+EPMC+oILMeV6wiI1Y7ici7Vr07XC1gGjWKY4WkHakwvY4yyFUDAvMTujg1ousvswmHPMmImv04BqAh1/ge17TmkfpHKdBkg9Z1Gc5PvQxgm8kNGP4cR6o4Nb5qIOinzNvixLO9s92BAJdYyfcJHs2R3pUN7RsQy76BaGM5OVvrFatkGEvpn+uVqc1dlUUSdLRpiPhaDWrP5fGgpdnKdVe84a3J0pZDaoqAQuaRWt/hVN+Gj4f5dWB0g4IiuvSm50Do95Tmiod3sdXpMTzaDUd6AZto214n3e+zNg=
Content-Type: text/plain; charset="utf-8"
Content-ID: <A0244C485303F849868AFA57DA008D40@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ed4cae6f-a949-4099-d91e-08d6b73570bc
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2019 06:35:47.0807 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4236
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/03cTrrxDePjeDntJ3Oc42Ll3oh8>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 06:35:53 -0000

SGksDQoNCkkgc3VwcG9ydCB0aGUgYWRvcHRpbmcgdGhlIGRyYWZ0LCBhbmQgSSB3aWxsIHByb3Zp
ZGUgaW5wdXQgKEkgdGhpbmsgdGhlIGRyYWZ0IGlzIGluIHByZXR0eSBnb29kIHNoYXBlIGFscmVh
ZHkpIGFuZCByZXZpZXcgdGhlIGRvY3VtZW50Lg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoN
Cu+7v09uIDAxLzA0LzIwMTksIDIzLjQ2LCAic2lwY29yZSBvbiBiZWhhbGYgb2YgQS4gSmVhbiBN
YWhvbmV5IiA8c2lwY29yZS1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBtYWhvbmV5QG5v
c3RydW0uY29tPiB3cm90ZToNCg0KICAgIEhpIGFsbCwNCiAgICANCiAgICBUaGlzIGlzIGEgY2Fs
bCBmb3IgYWRvcHRpb24gb2YgZHJhZnQteXVzZWYtc2lwY29yZS1kaWdlc3Qtc2NoZW1lIGluIHRo
ZSANCiAgICBTSVBDT1JFIHdvcmtpbmcgZ3JvdXAuDQogICAgDQogICAgaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQteXVzZWYtc2lwY29yZS1kaWdlc3Qtc2NoZW1lLw0KICAg
IA0KICAgIFBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgdG8gdGhlIGxpc3Qgb3IgdG8gdGhlIGNo
YWlycyBieSBBcHJpbCAxNXRoLg0KICAgIA0KICAgIFRoYW5rcyENCiAgICANCiAgICBKZWFuDQog
ICAgDQogICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CiAgICBzaXBjb3JlIG1haWxpbmcgbGlzdA0KICAgIHNpcGNvcmVAaWV0Zi5vcmcNCiAgICBodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcGNvcmUNCiAgICANCg0K


From nobody Tue Apr  2 02:23:12 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F07B912009A; Tue,  2 Apr 2019 02:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 8WNTtG_BH9QW; Tue,  2 Apr 2019 02:23:06 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-ve1eur03on0618.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe09::618]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0D2012008B; Tue,  2 Apr 2019 02:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bYcQ4hwuoKgn1zObE8U82qPNHNshLgGeRKoJYm55d3M=; b=e6x4ucuQ9gdpb1GKDE52WT98wEFJc4lHaBpWhNEKTii4eNQ+EWrSKFW46307B8pq8qmDtLYPO4vFEvsKNMVVcm438LE/nx/qY+0jSLKXvakZ6TtQMp1ltxsSyZFLqX/CIVeV77XfCJfpTT192WOulObzHdsKNyoa/obSR1MhKCw=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3338.eurprd07.prod.outlook.com (10.170.247.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.6; Tue, 2 Apr 2019 09:23:02 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9%5]) with mapi id 15.20.1771.007; Tue, 2 Apr 2019 09:23:02 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Dale R. Worley" <worley@ariadne.com>, Roman Shpount <roman@telurix.com>
CC: "sipcore@ietf.org" <sipcore@ietf.org>, "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "adam@nostrum.com" <adam@nostrum.com>
Thread-Topic: [sipcore] reg-event issue with multi-identity/multi-device
Thread-Index: AQHU5dKIZHWL8hDqjUW2JMDFs9lEoaYiXI0AgAZ1boA=
Date: Tue, 2 Apr 2019 09:23:02 +0000
Message-ID: <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com>
References: <CAD5OKxs0PevSqthM5wp1=Q7OgrzuL71Gj=Y_tciKT7t7AVnNeA@mail.gmail.com> <8736n6la0k.fsf@hobgoblin.ariadne.com> <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com>
In-Reply-To: <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b168a299-0bf1-485f-7017-08d6b74cce48
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR07MB3338; 
x-ms-traffictypediagnostic: HE1PR07MB3338:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <HE1PR07MB3338D420C61C6949D9BF776C93560@HE1PR07MB3338.eurprd07.prod.outlook.com>
x-forefront-prvs: 0995196AA2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(346002)(396003)(136003)(366004)(189003)(199004)(54906003)(25786009)(2616005)(476003)(446003)(5660300002)(102836004)(316002)(11346002)(99286004)(33656002)(81166006)(106356001)(81156014)(58126008)(76176011)(6506007)(6436002)(110136005)(66066001)(97736004)(105586002)(8676002)(8936002)(186003)(14454004)(2906002)(229853002)(83716004)(6116002)(3846002)(36756003)(478600001)(82746002)(68736007)(26005)(7736002)(966005)(4326008)(53936002)(6246003)(44832011)(6486002)(305945005)(486006)(256004)(6306002)(14444005)(71190400001)(71200400001)(6512007)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3338; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: MNtzz+9FMhtQCvGjkIgOnCKPfg6Wt6TEG7fy67bajySzrCISxETp7yphSx3OEZG8RLdgKp90rbyrp2ySkF/UzfTlWiFt5OBw9Vmv55bkbX7G+EKWWBSxBU1e+P5mkVmEnXPzOLo9MuW4b21Wm3igqSKYLKnyuXcAcGSF8b8ghECubsM2s2neTKMaW16oyA+t2Fiw8M0ewL+r8F4eodRpSXRQYwmTAU5ItRBT33eVTU0hFjJDEEyLSdUlQFd2Eow7ZNlUGee3NG2Zp8y/yhOKNpRy9zSzhofLuLqwdqcseiFHWwxfiFOYDTrtswrlEoyxGAHm4VxU1IgN/6tndB0cS+MGbH38lOE6kSqX3DHTIdHEN0vayIpxX3g9WXGdCqVkCEXAUALnrBtYcc3vrwcfDHvOJhgYpADTAkIro7mVm2E=
Content-Type: text/plain; charset="utf-8"
Content-ID: <498B3F1A176CDC41ADA161E993F5AC8E@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b168a299-0bf1-485f-7017-08d6b74cce48
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2019 09:23:02.4554 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3338
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/-XlmKWGlz9gz96JVLxOWhgrRLpA>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 09:23:10 -0000

SGksDQoNCkknZCBsaWtlIHRvIGFzayB0aGUgY2hhaXJzIGFuZCBBRCBvbiBzb21lIGd1aWRhbmNl
IG9uIGhvdyB0byBtb3ZlIGZvcndhcmQgd2l0aCB0aGlzLiBUaGVyZSBzZWVtcyB0byBiZSBpbnRl
cmVzdCBpbiB0aGUgaXNzdWUuDQoNCkFzIEkgaGF2ZSBpbmRpY2F0ZWQsIEkgKnBlcnNvbmFsbHkq
IHRoaW5rIHRoZSByZWFsIHByb2JsZW0gaXMgZHVwbGljYXRpb24gb2YgZGF0YSwgc28gc2ltcGx5
IGNvbXByZXNzaW5nIGl0IGRvZXMgbm90IHJlYWxseSBzb2x2ZSB0aGUgcHJvYmxlbSBsb25ndGVy
bSwgYW5kIHRoYXQgaXMgdGhlIGlucHV0IEkgaGF2ZSByZWNlaXZlZCBmcm9tIG90aGVycyB0b28u
DQoNCldlIGZvciBzdXJlIG5lZWQgdG8gdGFrZSBPdXRib3VuZCAocmVhZDogcmVnLWlkIGFuZCBp
bnN0YW5jZS1pZCkgaW50byBjb25zaWRlcmF0aW9uLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0K
DQoNCg0K77u/T24gMjkvMDMvMjAxOSwgOS40NSwgInNpcGNvcmUgb24gYmVoYWxmIG9mIENocmlz
dGVyIEhvbG1iZXJnIiA8c2lwY29yZS1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBjaHJp
c3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KDQogICAgSGkgRGFsZSwNCiAgICAN
CiAgICA+U28gYW55IHNjaGVtZSBmb3IgYWJyaWRnaW5nIHJlZ2lzdHJhdGlvbiBldmVudHMgaXMg
bGlrZWx5IHRvIGhhdmUgdG8NCiAgICA+ZGVhbCB3aXRoIHVuaXF1ZXNzIGluIHRoZSA8dXJpPiBh
bmQgJ2lkJyBzdHJpbmdzLg0KICAgIA0KICAgIE15IGFzc3VtcHRpb24gaXMgdGhhdCB0aGUgPHVy
aT4gYW5kICdpZCcgYXJlIHVuaXF1ZSBmb3IgZWFjaCBjb250YWN0LiAgICANCiAgICANCiAgICA+
ICAgIEEgYmV0dGVyIHdheSB0byBqdWRnZSB0aGlzIGlzIHRvIGxvb2sgYXQgYSAqcmVhbCogcmVn
aXN0cmF0aW9uIGV2ZW50IGZvcg0KICAgID4gICAgYSBzaXR1YXRpb24gbGlrZSB0aGlzIC0tIHNh
eSwgdGhyZWUgVUFzIHJlZ2lzdGVyZWQgZm9yIHRoZSBzYW1lIHRocmVlDQogICAgPiAgICBBT1Jz
LiAgRG9lcyBhbnlvbmUgaGF2ZSBhbnkgZXhhbXBsZXMgdG8gc2hhcmU/DQogICAgDQogICAgVGhl
IGV4YW1wbGUgSSBnYXZlIHdhcyByZWZsZWN0aW5nIGEgcmVhbCBkZXBsb3ltZW50IHNjZW5hcmlv
Lg0KICAgIA0KICAgIFJlZ2FyZHMsDQogICAgDQogICAgQ2hyaXN0ZXINCiAgICANCiAgICANCiAg
ICANCiAgICBPbiAyOS8wMy8yMDE5LCAzLjU1LCAiRGFsZSBSLiBXb3JsZXkiIDx3b3JsZXlAYXJp
YWRuZS5jb20+IHdyb3RlOg0KICAgIA0KICAgICAgICBSb21hbiBTaHBvdW50IDxyb21hbkB0ZWx1
cml4LmNvbT4gd3JpdGVzOg0KICAgICAgICA+IFNob3VsZCBub3QgZWFjaCByZWdpc3RyYXRpb24g
ZW50cnkgaGF2ZSBhIGRpZmZlcmVudCBpbnN0YW5jZS1pZC9yZWctaWQNCiAgICAgICAgPiAoZGVm
aW5lZCBpbiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNTYyNikgaW4gdW5rbm93bi1w
YXJhbQ0KICAgICAgICA+IGF0dHJpYnV0ZXM/DQogICAgICAgIA0KICAgICAgICBMb29raW5nIGF0
IHRoZSBleGFtcGxlIG1vcmUgY2FyZWZ1bGx5LiAgVGhlIHR5cGljYWwgPHJlZ2lzdHJhdGlvbj4g
c3RhcnQNCiAgICAgICAgdGFnIGFuZCB0aGUgdHlwaWNhbCA8Y29udGFjdD4gZWxlbWVudCBsb29r
IGxpa2UgdGhpczoNCiAgICAgICAgDQogICAgICAgIDx0bnM6cmVnaXN0cmF0aW9uIGlkPSIxMjM0
NTY3ODkwIiBhb3I9InNpcDptYWlsdG86KzE1NTU2NjY3Nzc3QGltcy5tbmMwMDEubWNjMDAxLjNn
cHBuZXR3b3Jrcy5vcmciPg0KICAgICAgICAgICAgPHRuczpjb250YWN0IGV2ZW50PSJyZWdpc3Rl
cmVkIiBpZD0iMjM0NTY3ODkwMSIgZHVyYXRpb24tcmVnaXN0ZXJlZD0iNDI5NDk2NzI5NSINCiAg
ICAgICAgCSBjc2VxPSI0Mjk0OTY3Mjk1IiByZXRyeS1hZnRlcj0iNDI5NDk2NzI5NSIgcT0iMCIg
c3RhdGU9ImFjdGl2ZSINCiAgICAgICAgCSBjYWxsaWQ9IlN0cmluZyIgZXhwaXJlcz0iNDI5NDk2
NzI5NSI+DQogICAgICAgICAgICAgIDx0bnM6dXJpPnNpcDorMTU1NTY2Njc3NzdAWzIwMDE6MGRi
ODo4NWEzOjAwMDA6MDAwMDo4YTJlOjAzNzA6YWFhYV08L3Ruczp1cmk+DQogICAgICAgICAgICAg
IDx0bnM6ZGlzcGxheS1uYW1lIHhtbDpsYW5nPSJlbi11cyI+U3RyaW5nPC90bnM6ZGlzcGxheS1u
YW1lPg0KICAgICAgICAgICAgICA8dG5zOnVua25vd24tcGFyYW0gbmFtZT0iU3RyaW5nIj5TdHJp
bmc8L3Ruczp1bmtub3duLXBhcmFtPg0KICAgICAgICAgICAgPC90bnM6Y29udGFjdD4NCiAgICAg
ICAgDQogICAgICAgIEFzIEkgcmVhZCBSRkMgMzY4MCwgdGhlIGlkIGF0dHJpYnV0ZSBvZiA8cmVn
aXN0cmF0aW9uPiBhbmQgdGhlIGlkDQogICAgICAgIGF0dHJpYnV0ZSBvZiA8Y29udGFjdD4gaGF2
ZSB0byBiZSB1bmlxdWUgd2l0aGluIHRoZSA8cmVnaW5mbz4uDQogICAgICAgIA0KICAgICAgICBU
aGUgYWN0dWFsIG5hbWUgb2YgdGhlIEFPUiBkaXNwbGF5ZWQgdG8gdGhlIHVzZXIgb24gdGhlIGRl
dmljZSBpcyBsaWtlbHkNCiAgICAgICAgdG8gYmUgY3VzdG9taXplZCwgYnV0IEkgd2FzIHByb2Jh
Ymx5IHdyb25nIHJlZ2FyZGluZyB0aGUgPGRpc3BsYXktbmFtZT4NCiAgICAgICAgZWxlbWVudCBo
ZXJlIC0tIGl0J3MgdGFrZW4gZnJvbSB0aGUgQ29udGFjdCBoZWFkZXIgaW4gdGhlIFJFR0lTVEVS
DQogICAgICAgIHJlcXVlc3QsIGFuZCBtb3N0IGxpa2VseSBpcyBlbXB0eS4NCiAgICAgICAgDQog
ICAgICAgIFRoZSBzaXAuaW5zdGFuY2UgaW4gdGhlIENvbnRhY3Qgd2lsbCBzaG93IHVwIGFzIGFu
IDx1bmtub3duLXBhcmFtPg0KICAgICAgICBlbGVtZW50LCBidXQgaXQgc2hvdWxkIGJlIHRoZSBz
YW1lIGZvciBhbGwgPGNvbnRhY3Q+IGVsZW1lbnRzIGZvcg0KICAgICAgICByZWdpc3RyYXRpb25z
IGZyb20gdGhlIHNhbWUgVUEuDQogICAgICAgIA0KICAgICAgICBUaGUgPHVyaT4gZWxlbWVudCAt
LSB0aGUgY29udGFjdCBVUkkgLS0gaXMgbGlrZWx5IHRvIGNvbnRhaW4gYm90aCBzb21lDQogICAg
ICAgIHBhcnQgb2YgdGhlIEFPUiBhbmQgdGhlIElQIGFkZHJlc3Mgb2YgdGhlIFVBLCBhbmQgc28g
dGhleSdyZSBsaWtlbHkgdG8NCiAgICAgICAgYmUgZGlmZmVyZW50IGZvciBldmVyeSA8Y29udGFj
dD4gZWxlbWVudC4NCiAgICAgICAgDQogICAgICAgIFNvIGFueSBzY2hlbWUgZm9yIGFicmlkZ2lu
ZyByZWdpc3RyYXRpb24gZXZlbnRzIGlzIGxpa2VseSB0byBoYXZlIHRvDQogICAgICAgIGRlYWwg
d2l0aCB1bmlxdWVzcyBpbiB0aGUgPHVyaT4gYW5kICdpZCcgc3RyaW5ncy4NCiAgICAgICAgDQog
ICAgICAgIEEgYmV0dGVyIHdheSB0byBqdWRnZSB0aGlzIGlzIHRvIGxvb2sgYXQgYSAqcmVhbCog
cmVnaXN0cmF0aW9uIGV2ZW50IGZvcg0KICAgICAgICBhIHNpdHVhdGlvbiBsaWtlIHRoaXMgLS0g
c2F5LCB0aHJlZSBVQXMgcmVnaXN0ZXJlZCBmb3IgdGhlIHNhbWUgdGhyZWUNCiAgICAgICAgQU9S
cy4gIERvZXMgYW55b25lIGhhdmUgYW55IGV4YW1wbGVzIHRvIHNoYXJlPw0KICAgICAgICANCiAg
ICAgICAgRGFsZQ0KICAgICAgICANCiAgICANCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KICAgIHNpcGNvcmUgbWFpbGluZyBsaXN0DQogICAgc2lw
Y29yZUBpZXRmLm9yZw0KICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
c2lwY29yZQ0KICAgIA0KDQo=


From nobody Tue Apr  2 07:35:19 2019
Return-Path: <br@brianrosen.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57AE5120133 for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 07:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 GW0jdFvljVBd for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 07:35:16 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 E12261200DB for <sipcore@ietf.org>; Tue,  2 Apr 2019 07:35:15 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id k14so15513220qtb.0 for <sipcore@ietf.org>; Tue, 02 Apr 2019 07:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LonGV5NqMcDwmefh7V1YMq/yyixguANqSuv3Cm2BBLo=; b=y/KiPA8/PrBAVjs5qL8WD1LoL2+ddIozdhtqY5Z2bgvEOE0WHALE/F8ExPb8ssWr/B aljZKH0b8bxU8D8CxknMy25HJ9SKlygxM13a7fxkRKW3KA+DxPbqn+4iD35c+PcPuQY5 dP9nKFTGmmQBapDwb0QsLQoGdI7FhyU9XCTnGh1G+2jRDcW861ltTyEhzBVv92GDl77l pQqhq6IgN1j189kY0Abka0ceuiyARobmpMKzwwP/Kj+VGl293AbbUJmIhPvJ0mdoHith Qn0WoiYm/3sb1ByUqyvJLM1dB1pV+0mxNbeJ44OyaD68D8T5fk6iRmcJiOh6WfNY5p5f uGMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LonGV5NqMcDwmefh7V1YMq/yyixguANqSuv3Cm2BBLo=; b=YdhRUCscciMn1nZTumP4nlLhNNsDaRW3lgVkEJDzaRpxggo890gw0swrCYAjSTSjqO Iq9nByHDkobXBjUb775n90O5KTwsv4zJiTVbA2/+iF4EQEIVYggqgQaISMFBzlafZ4Wp rbARua+7duDOQpoTEsYhxHiFxL616fFP7Apts+/xek0QaTtW92jGqsHsOHWN5TEx3X2L dfYEPNaFYlaOxab9Hd384XkWfjgPGKt5liXTGqSA8A1L4+9xBztLd1YjC2O01P1kZeeo KME3MuFjrGtcjKWdtiP4w1DK8TE4BosfDGqXiBYk+B3PqpUs6dnbnHgRCNxqL6wDOpUw U81Q==
X-Gm-Message-State: APjAAAXnV6wGZpCHvsusAb/gsGapidg3iUUbhAqyMl1Qvq+09jAGjeAX t1Ly5VAyedDLlqsuElfAh5fj1Se3oag=
X-Google-Smtp-Source: APXvYqzD6l54c6zAf8vqOVBrNIi6BSf9OsKT/BhH29iLXZuAr+StKsgkF+duKebd2l1TTu1sKJC7Cg==
X-Received: by 2002:ac8:355c:: with SMTP id z28mr48378849qtb.286.1554215714943;  Tue, 02 Apr 2019 07:35:14 -0700 (PDT)
Received: from brians-mbp-3.lan ([24.129.255.66]) by smtp.gmail.com with ESMTPSA id v39sm8163005qtj.20.2019.04.02.07.35.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 07:35:14 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <F6F9524E-B17C-47DC-8C6D-B7A87FDFF007@ericsson.com>
Date: Tue, 2 Apr 2019 10:35:13 -0400
Cc: "A. Jean Mahoney" <mahoney@nostrum.com>, SIPCORE <sipcore@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BBA9452-9798-4E98-BBB9-9EC308BA4106@brianrosen.net>
References: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com> <F6F9524E-B17C-47DC-8C6D-B7A87FDFF007@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/f_fX-ZEbNShnXpFcjRutGY5ys8E>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 14:35:18 -0000

<As individual>
I support adopting this draft, and the NENA folks need it.  I wonder if =
we should expressly allow any new entries to the RFC7616 registry to be =
used.

Brian

> On Apr 2, 2019, at 2:35 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> I support the adopting the draft, and I will provide input (I think =
the draft is in pretty good shape already) and review the document.
>=20
> Regards,
>=20
> Christer
>=20
>=20
> =EF=BB=BFOn 01/04/2019, 23.46, "sipcore on behalf of A. Jean Mahoney" =
<sipcore-bounces@ietf.org on behalf of mahoney@nostrum.com> wrote:
>=20
>    Hi all,
>=20
>    This is a call for adoption of draft-yusef-sipcore-digest-scheme in =
the=20
>    SIPCORE working group.
>=20
>    https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/
>=20
>    Please send your comments to the list or to the chairs by April =
15th.
>=20
>    Thanks!
>=20
>    Jean
>=20
>    _______________________________________________
>    sipcore mailing list
>    sipcore@ietf.org
>    https://www.ietf.org/mailman/listinfo/sipcore
>=20
>=20
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore


From nobody Tue Apr  2 08:34:01 2019
Return-Path: <roman@telurix.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4257B120166 for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 08:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
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 tesZ6-1XWXmJ for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 08:33:57 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 72385120155 for <sipcore@ietf.org>; Tue,  2 Apr 2019 08:33:53 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id e24so6549257pfi.12 for <sipcore@ietf.org>; Tue, 02 Apr 2019 08:33:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rXYnoA7k7ouFVZ4wg3zvh42qVZ6GydDfNzd1NdHoXYw=; b=Ej0jdNMbw6kta2uUDtXzxWFpW7YUWpgY4h5hQpFW4jl2atQGNHU0ib6gF+VpmYqHjO DZv4Dab4hkupTHAZch2kqfO4T134q2TW59oYX1SFNLkGmaNk/LouAdjDuxD6V9HIlKCl MeMCoAQDrNupTr0uyPh+pjhgWHrqyVLkl4xiwfT08WPNmMaU4ZUX62LX0DGomXiEyHR9 BstRoFUrfhB7RrNVSZ+3p1/gHo9L71NPgBZE4x4B+tTPh+qq/n/74xPaPSSMnUqp5Usk i6GJ1TWaKTktRoOB1iw4tPfTllfinrtl6q+NlJ7H0I4Xso2xqH0b8+OwHwk8F8d6lR8m Z/mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rXYnoA7k7ouFVZ4wg3zvh42qVZ6GydDfNzd1NdHoXYw=; b=qq9ji1rWw7UImPocjJmq0PeLbZHwP+NiBhM1GCKFO1rPtIgWuMOb4rzD+DgGK51BO5 nOLIPEvHWY0g/DOf9qQ23071FXbGNvAgDoZv1Yu+1T5iBPfpnxADH5NEoFu1TfzTeEtP FWgwp/d9nm9SjYOIKEGtxiDgPFLM92uzIQZN2y3Ftbd7GjwFHaYXvn2A3GUsE8jy08ie IYF8905ke38NRdGrtAf9sNkbw3ax9MVYAo24dUUYewX8NoBI13yd1C92riB/RCZcn8jg mQ5Ny9Sdm5wjl8AhNR3SG+s+GbHoTTkam1XJZ2GDb2/t5vw6ccQm351d0RzXD2Ti+6L/ cCBA==
X-Gm-Message-State: APjAAAWtty4QMz2X/+JOY+jHjs8yS01yy3kmpzWYgvr8Am8glC5pF18e ND7flY/UNAPC7RIpQWLh66far0BM39A=
X-Google-Smtp-Source: APXvYqy4HVnGtY4BJujdMXrFoeZO/3cN6JDcXHUc2pQsQIxg5nUZjxEGj797NCHSf2expaoSASlJYA==
X-Received: by 2002:a65:4689:: with SMTP id h9mr40822667pgr.295.1554219230411;  Tue, 02 Apr 2019 08:33:50 -0700 (PDT)
Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com. [209.85.215.176]) by smtp.gmail.com with ESMTPSA id h10sm21564835pfj.79.2019.04.02.08.33.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 08:33:49 -0700 (PDT)
Received: by mail-pg1-f176.google.com with SMTP id g8so6763665pgf.2; Tue, 02 Apr 2019 08:33:48 -0700 (PDT)
X-Received: by 2002:a62:2a97:: with SMTP id q145mr70628590pfq.22.1554219228340;  Tue, 02 Apr 2019 08:33:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5OKxs0PevSqthM5wp1=Q7OgrzuL71Gj=Y_tciKT7t7AVnNeA@mail.gmail.com> <8736n6la0k.fsf@hobgoblin.ariadne.com> <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com> <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com>
In-Reply-To: <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 2 Apr 2019 11:33:40 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsEdKD1x_A4Mc8kbMJ90cx63U2jd4EP+DmuCs9N87_swA@mail.gmail.com>
Message-ID: <CAD5OKxsEdKD1x_A4Mc8kbMJ90cx63U2jd4EP+DmuCs9N87_swA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>,  "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "adam@nostrum.com" <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="000000000000022b2205858ddd15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Yiu_L4mSI7MkQjr2KyURmKCYO8A>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 15:33:59 -0000

--000000000000022b2205858ddd15
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think RFC 3680 is due for payload schema update.

One thing that always bothered me about RFC 3680 was that it does not
expose RFC 3327 Path information.

Regards,
_____________
Roman Shpount


On Tue, Apr 2, 2019 at 5:23 AM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> I'd like to ask the chairs and AD on some guidance on how to move forward
> with this. There seems to be interest in the issue.
>
> As I have indicated, I *personally* think the real problem is duplication
> of data, so simply compressing it does not really solve the problem
> longterm, and that is the input I have received from others too.
>
> We for sure need to take Outbound (read: reg-id and instance-id) into
> consideration.
>
> Regards,
>
> Christer
>
>
>
> =EF=BB=BFOn 29/03/2019, 9.45, "sipcore on behalf of Christer Holmberg" <
> sipcore-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
>
>     Hi Dale,
>
>     >So any scheme for abridging registration events is likely to have to
>     >deal with uniquess in the <uri> and 'id' strings.
>
>     My assumption is that the <uri> and 'id' are unique for each contact.
>
>
>     >    A better way to judge this is to look at a *real* registration
> event for
>     >    a situation like this -- say, three UAs registered for the same
> three
>     >    AORs.  Does anyone have any examples to share?
>
>     The example I gave was reflecting a real deployment scenario.
>
>     Regards,
>
>     Christer
>
>
>
>     On 29/03/2019, 3.55, "Dale R. Worley" <worley@ariadne.com> wrote:
>
>         Roman Shpount <roman@telurix.com> writes:
>         > Should not each registration entry have a different
> instance-id/reg-id
>         > (defined in https://tools.ietf.org/html/rfc5626) in
> unknown-param
>         > attributes?
>
>         Looking at the example more carefully.  The typical <registration=
>
> start
>         tag and the typical <contact> element look like this:
>
>         <tns:registration id=3D"1234567890" aor=3D"sip:mailto:+
> 15556667777@ims.mnc001.mcc001.3gppnetworks.org">
>             <tns:contact event=3D"registered" id=3D"2345678901"
> duration-registered=3D"4294967295"
>                  cseq=3D"4294967295" retry-after=3D"4294967295" q=3D"0"
> state=3D"active"
>                  callid=3D"String" expires=3D"4294967295">
>               <tns:uri>sip:+15556667777@
> [2001:0db8:85a3:0000:0000:8a2e:0370:aaaa]</tns:uri>
>               <tns:display-name xml:lang=3D"en-us">String</tns:display-na=
me>
>               <tns:unknown-param name=3D"String">String</tns:unknown-para=
m>
>             </tns:contact>
>
>         As I read RFC 3680, the id attribute of <registration> and the id
>         attribute of <contact> have to be unique within the <reginfo>.
>
>         The actual name of the AOR displayed to the user on the device is
> likely
>         to be customized, but I was probably wrong regarding the
> <display-name>
>         element here -- it's taken from the Contact header in the REGISTE=
R
>         request, and most likely is empty.
>
>         The sip.instance in the Contact will show up as an <unknown-param=
>
>         element, but it should be the same for all <contact> elements for
>         registrations from the same UA.
>
>         The <uri> element -- the contact URI -- is likely to contain both
> some
>         part of the AOR and the IP address of the UA, and so they're
> likely to
>         be different for every <contact> element.
>
>         So any scheme for abridging registration events is likely to have
> to
>         deal with uniquess in the <uri> and 'id' strings.
>
>         A better way to judge this is to look at a *real* registration
> event for
>         a situation like this -- say, three UAs registered for the same
> three
>         AORs.  Does anyone have any examples to share?
>
>         Dale
>
>
>     _______________________________________________
>     sipcore mailing list
>     sipcore@ietf.org
>     https://www.ietf.org/mailman/listinfo/sipcore
>
>
>

--000000000000022b2205858ddd15
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think RFC 3680 is due for payload schema update.<div><br=
></div><div>One thing that always bothered me about RFC 3680 was that it do=
es not expose RFC 3327 Path information.</div><div><br></div><div>Regards,<=
br></div><div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmai=
l=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br></div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Tue, Apr 2, 2019 at 5:23 AM Christer Holmberg &lt;<a href=3D"mailto:chris=
ter.holmberg@ericsson.com">christer.holmberg@ericsson.com</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I&#39;d like to ask the chairs and AD on some guidance on how to move forwa=
rd with this. There seems to be interest in the issue.<br>
<br>
As I have indicated, I *personally* think the real problem is duplication o=
f data, so simply compressing it does not really solve the problem longterm=
, and that is the input I have received from others too.<br>
<br>
We for sure need to take Outbound (read: reg-id and instance-id) into consi=
deration.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<br>
=EF=BB=BFOn 29/03/2019, 9.45, &quot;sipcore on behalf of Christer Holmberg&=
quot; &lt;<a href=3D"mailto:sipcore-bounces@ietf.org" target=3D"_blank">sip=
core-bounces@ietf.org</a> on behalf of <a href=3D"mailto:christer.holmberg@=
ericsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt; wrot=
e:<br>
<br>
=C2=A0 =C2=A0 Hi Dale,<br>
<br>
=C2=A0 =C2=A0 &gt;So any scheme for abridging registration events is likely=
 to have to<br>
=C2=A0 =C2=A0 &gt;deal with uniquess in the &lt;uri&gt; and &#39;id&#39; st=
rings.<br>
<br>
=C2=A0 =C2=A0 My assumption is that the &lt;uri&gt; and &#39;id&#39; are un=
ique for each contact.=C2=A0 =C2=A0 <br>
<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 A better way to judge this is to look at a =
*real* registration event for<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 a situation like this -- say, three UAs reg=
istered for the same three<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 AORs.=C2=A0 Does anyone have any examples t=
o share?<br>
<br>
=C2=A0 =C2=A0 The example I gave was reflecting a real deployment scenario.=
<br>
<br>
=C2=A0 =C2=A0 Regards,<br>
<br>
=C2=A0 =C2=A0 Christer<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 On 29/03/2019, 3.55, &quot;Dale R. Worley&quot; &lt;<a href=
=3D"mailto:worley@ariadne.com" target=3D"_blank">worley@ariadne.com</a>&gt;=
 wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Roman Shpount &lt;<a href=3D"mailto:roman@telur=
ix.com" target=3D"_blank">roman@telurix.com</a>&gt; writes:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Should not each registration entry have a =
different instance-id/reg-id<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; (defined in <a href=3D"https://tools.ietf.=
org/html/rfc5626" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.o=
rg/html/rfc5626</a>) in unknown-param<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; attributes?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Looking at the example more carefully.=C2=A0 Th=
e typical &lt;registration&gt; start<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 tag and the typical &lt;contact&gt; element loo=
k like this:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;tns:registration id=3D&quot;1234567890&quot=
; aor=3D&quot;sip:mailto:+<a href=3D"mailto:15556667777@ims.mnc001.mcc001.3=
gppnetworks.org" target=3D"_blank">15556667777@ims.mnc001.mcc001.3gppnetwor=
ks.org</a>&quot;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;tns:contact event=3D&quot;reg=
istered&quot; id=3D&quot;2345678901&quot; duration-registered=3D&quot;42949=
67295&quot;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cseq=3D&quot;=
4294967295&quot; retry-after=3D&quot;4294967295&quot; q=3D&quot;0&quot; sta=
te=3D&quot;active&quot;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0callid=3D&quo=
t;String&quot; expires=3D&quot;4294967295&quot;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;tns:uri&gt;sip:+155566=
67777@[2001:0db8:85a3:0000:0000:8a2e:0370:aaaa]&lt;/tns:uri&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;tns:display-name xml:l=
ang=3D&quot;en-us&quot;&gt;String&lt;/tns:display-name&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;tns:unknown-param name=
=3D&quot;String&quot;&gt;String&lt;/tns:unknown-param&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;/tns:contact&gt;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 As I read RFC 3680, the id attribute of &lt;reg=
istration&gt; and the id<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 attribute of &lt;contact&gt; have to be unique =
within the &lt;reginfo&gt;.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The actual name of the AOR displayed to the use=
r on the device is likely<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to be customized, but I was probably wrong rega=
rding the &lt;display-name&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 element here -- it&#39;s taken from the Contact=
 header in the REGISTER<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 request, and most likely is empty.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The sip.instance in the Contact will show up as=
 an &lt;unknown-param&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 element, but it should be the same for all &lt;=
contact&gt; elements for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 registrations from the same UA.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The &lt;uri&gt; element -- the contact URI -- i=
s likely to contain both some<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 part of the AOR and the IP address of the UA, a=
nd so they&#39;re likely to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 be different for every &lt;contact&gt; element.=
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 So any scheme for abridging registration events=
 is likely to have to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 deal with uniquess in the &lt;uri&gt; and &#39;=
id&#39; strings.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 A better way to judge this is to look at a *rea=
l* registration event for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a situation like this -- say, three UAs registe=
red for the same three<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 AORs.=C2=A0 Does anyone have any examples to sh=
are?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Dale<br>
<br>
<br>
=C2=A0 =C2=A0 _______________________________________________<br>
=C2=A0 =C2=A0 sipcore mailing list<br>
=C2=A0 =C2=A0 <a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore=
@ietf.org</a><br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sip=
core</a><br>
<br>
<br>
</blockquote></div>

--000000000000022b2205858ddd15--


From nobody Tue Apr  2 11:45:43 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5453120196; Tue,  2 Apr 2019 11:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 MANOsQLVTbTn; Tue,  2 Apr 2019 11:45:37 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-he1eur02on0622.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe05::622]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE1A5120170; Tue,  2 Apr 2019 11:45:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AvMJPvIGe4ChFRr5DHayq4J4j/JYvIOnBWPUSqkgqig=; b=h2iIeZzBFLZuYo2Enm21D5/HSGqIyNLahjgS6my7sS6PlNNqd+4iRdrm1aSPtYDGC5W9KwmRTwMqi9PWgkpjhwWGW3r8e+OWgDfd1dgZ0BjsRCgTmcy2dhvzIioDeGTFEVrU7xiXcb++2Ng3M8/9SNa42Rxt+t24B99NtKrun5E=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB4170.eurprd07.prod.outlook.com (20.176.166.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.6; Tue, 2 Apr 2019 18:45:33 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9%5]) with mapi id 15.20.1771.007; Tue, 2 Apr 2019 18:45:33 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
CC: "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>, "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "adam@nostrum.com" <adam@nostrum.com>
Thread-Topic: [sipcore] reg-event issue with multi-identity/multi-device
Thread-Index: AQHU5dKIZHWL8hDqjUW2JMDFs9lEoaYiXI0AgAZ1boCAADVEAIAAZ+YA
Date: Tue, 2 Apr 2019 18:45:33 +0000
Message-ID: <0EAFEA5B-B901-417E-812D-1511ADA0F741@ericsson.com>
References: <CAD5OKxs0PevSqthM5wp1=Q7OgrzuL71Gj=Y_tciKT7t7AVnNeA@mail.gmail.com> <8736n6la0k.fsf@hobgoblin.ariadne.com> <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com> <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com> <CAD5OKxsEdKD1x_A4Mc8kbMJ90cx63U2jd4EP+DmuCs9N87_swA@mail.gmail.com>
In-Reply-To: <CAD5OKxsEdKD1x_A4Mc8kbMJ90cx63U2jd4EP+DmuCs9N87_swA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [178.55.143.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9c75e02f-d587-4abf-0b03-08d6b79b6352
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:HE1PR07MB4170; 
x-ms-traffictypediagnostic: HE1PR07MB4170:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <HE1PR07MB41707DE06242093136C4FC3093560@HE1PR07MB4170.eurprd07.prod.outlook.com>
x-forefront-prvs: 0995196AA2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(39860400002)(376002)(396003)(136003)(189003)(199004)(54896002)(33656002)(14454004)(2616005)(66066001)(6512007)(71200400001)(53936002)(58126008)(3846002)(97736004)(186003)(105586002)(486006)(82746002)(7736002)(26005)(446003)(44832011)(6436002)(102836004)(76176011)(6486002)(6506007)(93886005)(36756003)(53546011)(99286004)(106356001)(476003)(256004)(229853002)(81156014)(14444005)(25786009)(81166006)(11346002)(5660300002)(6116002)(68736007)(6916009)(6246003)(8676002)(6306002)(236005)(606006)(71190400001)(966005)(316002)(4326008)(2906002)(478600001)(83716004)(54906003)(8936002)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4170; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: UsmEQbp+NDUlebASOOudlevOvn2C1eHSpd0QuXFtRdi5kb8kvN7y04z1o4P2uTPb0u4rCkdF2Lm/+xqnyWerchPo7rc1WzQI6cg7xc1EKWrID1ct/xmaMUIBZQe2X+1qSCFoSw8y8GyMGnfTJj532rQWUj2BTdIFMs7GtmrPPLIfX62eIdolzjIweS2kM1TkaLSNDspwyKwgJoQBlBvEzf8IO5By83pX1VasohBYmmvioQv+iiWtjsq94SECczRUuVcH3sLlzZ1CPmOpi1D7u2XUFk15KeajrjtjOVGQzpXiglYWGHYDfoV3vpEKimnhRK5uHS4vDBsrPHCmLPhsKRwb+Qd8y30fvktMuEFL4fBDXEW2nZnwKbBngHjqM5qu9a0bRY1H5dqCYv308h0BzIbtjuuNFzljV28jXKhpg0c=
Content-Type: multipart/alternative; boundary="_000_0EAFEA5BB901417E812D1511ADA0F741ericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9c75e02f-d587-4abf-0b03-08d6b79b6352
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2019 18:45:33.2798 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4170
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/KZp-4jab010CYfo9w6AgpVgJCeo>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 18:45:41 -0000

--_000_0EAFEA5BB901417E812D1511ADA0F741ericssoncom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCkp1c3QgdG8gY2xhcmlmeTogaWYgd2Ugd2FudCB0byBjaGFuZ2UgdGhlIHNjaGVtYSwg
SSB0aGluayBpdCBzaG91bGQgYmUgZG9uZSBhcyBhICpuZXcqIHNjaGVtYS4gV2Ugc2hvdWxkIGtl
ZXAgdGhlIG9sZCBzY2hlbWEgYXMgaXQgaXMsIG5vdCB0byBicmVhayBleGlzdGluZyBkZXBsb3lt
ZW50cy4NCg0KU28sIHdlIHdvdWxkIGhhdmUgdHdvIHNjaGVtYXMgKHRoZSBvbGQgb25lIGFuZCB0
aGUgbmV3IG9uZSksIGFuZCBvYnZpb3VzbHkgdGhlIGFzc29jaWF0ZWQgbWVjaGFuaXNtcyB0byBu
ZWdvdGlhdGUgYW5kIGluZGljYXRlIHN1cHBvcnQgb2YgdGhlbS4NCg0KUmVnYXJkcywNCg0KQ2hy
aXN0ZXINCg0KRnJvbTogUm9tYW4gU2hwb3VudCA8cm9tYW5AdGVsdXJpeC5jb20+DQpEYXRlOiBU
dWVzZGF5LCAyIEFwcmlsIDIwMTkgYXQgMTguMzQNClRvOiBDaHJpc3RlciBIb2xtYmVyZyA8Y2hy
aXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPg0KQ2M6IERhbGUgV29ybGV5IDx3b3JsZXlAYXJp
YWRuZS5jb20+LCAic2lwY29yZUBpZXRmLm9yZyIgPHNpcGNvcmVAaWV0Zi5vcmc+LCAic2lwY29y
ZS1jaGFpcnNAaWV0Zi5vcmciIDxzaXBjb3JlLWNoYWlyc0BpZXRmLm9yZz4sICJhZGFtQG5vc3Ry
dW0uY29tIiA8YWRhbUBub3N0cnVtLmNvbT4NClN1YmplY3Q6IFJlOiBbc2lwY29yZV0gcmVnLWV2
ZW50IGlzc3VlIHdpdGggbXVsdGktaWRlbnRpdHkvbXVsdGktZGV2aWNlDQoNCkkgdGhpbmsgUkZD
IDM2ODAgaXMgZHVlIGZvciBwYXlsb2FkIHNjaGVtYSB1cGRhdGUuDQoNCk9uZSB0aGluZyB0aGF0
IGFsd2F5cyBib3RoZXJlZCBtZSBhYm91dCBSRkMgMzY4MCB3YXMgdGhhdCBpdCBkb2VzIG5vdCBl
eHBvc2UgUkZDIDMzMjcgUGF0aCBpbmZvcm1hdGlvbi4NCg0KUmVnYXJkcywNCl9fX19fX19fX19f
X18NClJvbWFuIFNocG91bnQNCg0KDQpPbiBUdWUsIEFwciAyLCAyMDE5IGF0IDU6MjMgQU0gQ2hy
aXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hy
aXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4gd3JvdGU6DQpIaSwNCg0KSSdkIGxpa2UgdG8g
YXNrIHRoZSBjaGFpcnMgYW5kIEFEIG9uIHNvbWUgZ3VpZGFuY2Ugb24gaG93IHRvIG1vdmUgZm9y
d2FyZCB3aXRoIHRoaXMuIFRoZXJlIHNlZW1zIHRvIGJlIGludGVyZXN0IGluIHRoZSBpc3N1ZS4N
Cg0KQXMgSSBoYXZlIGluZGljYXRlZCwgSSAqcGVyc29uYWxseSogdGhpbmsgdGhlIHJlYWwgcHJv
YmxlbSBpcyBkdXBsaWNhdGlvbiBvZiBkYXRhLCBzbyBzaW1wbHkgY29tcHJlc3NpbmcgaXQgZG9l
cyBub3QgcmVhbGx5IHNvbHZlIHRoZSBwcm9ibGVtIGxvbmd0ZXJtLCBhbmQgdGhhdCBpcyB0aGUg
aW5wdXQgSSBoYXZlIHJlY2VpdmVkIGZyb20gb3RoZXJzIHRvby4NCg0KV2UgZm9yIHN1cmUgbmVl
ZCB0byB0YWtlIE91dGJvdW5kIChyZWFkOiByZWctaWQgYW5kIGluc3RhbmNlLWlkKSBpbnRvIGNv
bnNpZGVyYXRpb24uDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg0KDQpPbiAyOS8wMy8yMDE5
LCA5LjQ1LCAic2lwY29yZSBvbiBiZWhhbGYgb2YgQ2hyaXN0ZXIgSG9sbWJlcmciIDxzaXBjb3Jl
LWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnNpcGNvcmUtYm91bmNlc0BpZXRmLm9yZz4gb24gYmVo
YWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9s
bWJlcmdAZXJpY3Nzb24uY29tPj4gd3JvdGU6DQoNCiAgICBIaSBEYWxlLA0KDQogICAgPlNvIGFu
eSBzY2hlbWUgZm9yIGFicmlkZ2luZyByZWdpc3RyYXRpb24gZXZlbnRzIGlzIGxpa2VseSB0byBo
YXZlIHRvDQogICAgPmRlYWwgd2l0aCB1bmlxdWVzcyBpbiB0aGUgPHVyaT4gYW5kICdpZCcgc3Ry
aW5ncy4NCg0KICAgIE15IGFzc3VtcHRpb24gaXMgdGhhdCB0aGUgPHVyaT4gYW5kICdpZCcgYXJl
IHVuaXF1ZSBmb3IgZWFjaCBjb250YWN0Lg0KDQogICAgPiAgICBBIGJldHRlciB3YXkgdG8ganVk
Z2UgdGhpcyBpcyB0byBsb29rIGF0IGEgKnJlYWwqIHJlZ2lzdHJhdGlvbiBldmVudCBmb3INCiAg
ICA+ICAgIGEgc2l0dWF0aW9uIGxpa2UgdGhpcyAtLSBzYXksIHRocmVlIFVBcyByZWdpc3RlcmVk
IGZvciB0aGUgc2FtZSB0aHJlZQ0KICAgID4gICAgQU9Scy4gIERvZXMgYW55b25lIGhhdmUgYW55
IGV4YW1wbGVzIHRvIHNoYXJlPw0KDQogICAgVGhlIGV4YW1wbGUgSSBnYXZlIHdhcyByZWZsZWN0
aW5nIGEgcmVhbCBkZXBsb3ltZW50IHNjZW5hcmlvLg0KDQogICAgUmVnYXJkcywNCg0KICAgIENo
cmlzdGVyDQoNCg0KDQogICAgT24gMjkvMDMvMjAxOSwgMy41NSwgIkRhbGUgUi4gV29ybGV5IiA8
d29ybGV5QGFyaWFkbmUuY29tPG1haWx0bzp3b3JsZXlAYXJpYWRuZS5jb20+PiB3cm90ZToNCg0K
ICAgICAgICBSb21hbiBTaHBvdW50IDxyb21hbkB0ZWx1cml4LmNvbTxtYWlsdG86cm9tYW5AdGVs
dXJpeC5jb20+PiB3cml0ZXM6DQogICAgICAgID4gU2hvdWxkIG5vdCBlYWNoIHJlZ2lzdHJhdGlv
biBlbnRyeSBoYXZlIGEgZGlmZmVyZW50IGluc3RhbmNlLWlkL3JlZy1pZA0KICAgICAgICA+IChk
ZWZpbmVkIGluIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1NjI2KSBpbiB1bmtub3du
LXBhcmFtDQogICAgICAgID4gYXR0cmlidXRlcz8NCg0KICAgICAgICBMb29raW5nIGF0IHRoZSBl
eGFtcGxlIG1vcmUgY2FyZWZ1bGx5LiAgVGhlIHR5cGljYWwgPHJlZ2lzdHJhdGlvbj4gc3RhcnQN
CiAgICAgICAgdGFnIGFuZCB0aGUgdHlwaWNhbCA8Y29udGFjdD4gZWxlbWVudCBsb29rIGxpa2Ug
dGhpczoNCg0KICAgICAgICA8dG5zOnJlZ2lzdHJhdGlvbiBpZD0iMTIzNDU2Nzg5MCIgYW9yPSJz
aXA6bWFpbHRvOisxNTU1NjY2Nzc3N0BpbXMubW5jMDAxLm1jYzAwMS4zZ3BwbmV0d29ya3Mub3Jn
PG1haWx0bzoxNTU1NjY2Nzc3N0BpbXMubW5jMDAxLm1jYzAwMS4zZ3BwbmV0d29ya3Mub3JnPiI+
DQogICAgICAgICAgICA8dG5zOmNvbnRhY3QgZXZlbnQ9InJlZ2lzdGVyZWQiIGlkPSIyMzQ1Njc4
OTAxIiBkdXJhdGlvbi1yZWdpc3RlcmVkPSI0Mjk0OTY3Mjk1Ig0KICAgICAgICAgICAgICAgICBj
c2VxPSI0Mjk0OTY3Mjk1IiByZXRyeS1hZnRlcj0iNDI5NDk2NzI5NSIgcT0iMCIgc3RhdGU9ImFj
dGl2ZSINCiAgICAgICAgICAgICAgICAgY2FsbGlkPSJTdHJpbmciIGV4cGlyZXM9IjQyOTQ5Njcy
OTUiPg0KICAgICAgICAgICAgICA8dG5zOnVyaT5zaXA6KzE1NTU2NjY3Nzc3QFsyMDAxOjBkYjg6
ODVhMzowMDAwOjAwMDA6OGEyZTowMzcwOmFhYWFdPC90bnM6dXJpPg0KICAgICAgICAgICAgICA8
dG5zOmRpc3BsYXktbmFtZSB4bWw6bGFuZz0iZW4tdXMiPlN0cmluZzwvdG5zOmRpc3BsYXktbmFt
ZT4NCiAgICAgICAgICAgICAgPHRuczp1bmtub3duLXBhcmFtIG5hbWU9IlN0cmluZyI+U3RyaW5n
PC90bnM6dW5rbm93bi1wYXJhbT4NCiAgICAgICAgICAgIDwvdG5zOmNvbnRhY3Q+DQoNCiAgICAg
ICAgQXMgSSByZWFkIFJGQyAzNjgwLCB0aGUgaWQgYXR0cmlidXRlIG9mIDxyZWdpc3RyYXRpb24+
IGFuZCB0aGUgaWQNCiAgICAgICAgYXR0cmlidXRlIG9mIDxjb250YWN0PiBoYXZlIHRvIGJlIHVu
aXF1ZSB3aXRoaW4gdGhlIDxyZWdpbmZvPi4NCg0KICAgICAgICBUaGUgYWN0dWFsIG5hbWUgb2Yg
dGhlIEFPUiBkaXNwbGF5ZWQgdG8gdGhlIHVzZXIgb24gdGhlIGRldmljZSBpcyBsaWtlbHkNCiAg
ICAgICAgdG8gYmUgY3VzdG9taXplZCwgYnV0IEkgd2FzIHByb2JhYmx5IHdyb25nIHJlZ2FyZGlu
ZyB0aGUgPGRpc3BsYXktbmFtZT4NCiAgICAgICAgZWxlbWVudCBoZXJlIC0tIGl0J3MgdGFrZW4g
ZnJvbSB0aGUgQ29udGFjdCBoZWFkZXIgaW4gdGhlIFJFR0lTVEVSDQogICAgICAgIHJlcXVlc3Qs
IGFuZCBtb3N0IGxpa2VseSBpcyBlbXB0eS4NCg0KICAgICAgICBUaGUgc2lwLmluc3RhbmNlIGlu
IHRoZSBDb250YWN0IHdpbGwgc2hvdyB1cCBhcyBhbiA8dW5rbm93bi1wYXJhbT4NCiAgICAgICAg
ZWxlbWVudCwgYnV0IGl0IHNob3VsZCBiZSB0aGUgc2FtZSBmb3IgYWxsIDxjb250YWN0PiBlbGVt
ZW50cyBmb3INCiAgICAgICAgcmVnaXN0cmF0aW9ucyBmcm9tIHRoZSBzYW1lIFVBLg0KDQogICAg
ICAgIFRoZSA8dXJpPiBlbGVtZW50IC0tIHRoZSBjb250YWN0IFVSSSAtLSBpcyBsaWtlbHkgdG8g
Y29udGFpbiBib3RoIHNvbWUNCiAgICAgICAgcGFydCBvZiB0aGUgQU9SIGFuZCB0aGUgSVAgYWRk
cmVzcyBvZiB0aGUgVUEsIGFuZCBzbyB0aGV5J3JlIGxpa2VseSB0bw0KICAgICAgICBiZSBkaWZm
ZXJlbnQgZm9yIGV2ZXJ5IDxjb250YWN0PiBlbGVtZW50Lg0KDQogICAgICAgIFNvIGFueSBzY2hl
bWUgZm9yIGFicmlkZ2luZyByZWdpc3RyYXRpb24gZXZlbnRzIGlzIGxpa2VseSB0byBoYXZlIHRv
DQogICAgICAgIGRlYWwgd2l0aCB1bmlxdWVzcyBpbiB0aGUgPHVyaT4gYW5kICdpZCcgc3RyaW5n
cy4NCg0KICAgICAgICBBIGJldHRlciB3YXkgdG8ganVkZ2UgdGhpcyBpcyB0byBsb29rIGF0IGEg
KnJlYWwqIHJlZ2lzdHJhdGlvbiBldmVudCBmb3INCiAgICAgICAgYSBzaXR1YXRpb24gbGlrZSB0
aGlzIC0tIHNheSwgdGhyZWUgVUFzIHJlZ2lzdGVyZWQgZm9yIHRoZSBzYW1lIHRocmVlDQogICAg
ICAgIEFPUnMuICBEb2VzIGFueW9uZSBoYXZlIGFueSBleGFtcGxlcyB0byBzaGFyZT8NCg0KICAg
ICAgICBEYWxlDQoNCg0KICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQogICAgc2lwY29yZSBtYWlsaW5nIGxpc3QNCiAgICBzaXBjb3JlQGlldGYub3Jn
PG1haWx0bzpzaXBjb3JlQGlldGYub3JnPg0KICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vc2lwY29yZQ0KDQo=

--_000_0EAFEA5BB901417E812D1511ADA0F741ericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <59634DCD63C7E145BB55E78A3F53F07C@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzAu
ODVwdCAyLjBjbSA3MC44NXB0IDIuMGNtO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk
U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkZJIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5IaSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPkp1c3QgdG8gY2xhcmlmeTogaWYgd2Ugd2FudCB0byBjaGFuZ2UgdGhlIHNjaGVtYSwgSSB0
aGluayBpdCBzaG91bGQgYmUgZG9uZSBhcyBhICo8Yj5uZXc8L2I+KiBzY2hlbWEuIFdlIHNob3Vs
ZCBrZWVwIHRoZSBvbGQgc2NoZW1hIGFzIGl0IGlzLCBub3QgdG8gYnJlYWsgZXhpc3RpbmcgZGVw
bG95bWVudHMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5Tbywgd2Ugd291bGQgaGF2ZSB0d28gc2NoZW1h
cyAodGhlIG9sZCBvbmUgYW5kIHRoZSBuZXcgb25lKSwgYW5kIG9idmlvdXNseSB0aGUgYXNzb2Np
YXRlZCBtZWNoYW5pc21zIHRvIG5lZ290aWF0ZSBhbmQgaW5kaWNhdGUgc3VwcG9ydCBvZiB0aGVt
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkNocmlzdGVy
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20g
MGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIu
MHB0O2NvbG9yOmJsYWNrIj5Gcm9tOiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2NvbG9yOmJsYWNrIj5Sb21hbiBTaHBvdW50ICZsdDtyb21hbkB0ZWx1cml4LmNvbSZn
dDs8YnI+DQo8Yj5EYXRlOiA8L2I+VHVlc2RheSwgMiBBcHJpbCAyMDE5IGF0IDE4LjM0PGJyPg0K
PGI+VG86IDwvYj5DaHJpc3RlciBIb2xtYmVyZyAmbHQ7Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nz
b24uY29tJmd0Ozxicj4NCjxiPkNjOiA8L2I+RGFsZSBXb3JsZXkgJmx0O3dvcmxleUBhcmlhZG5l
LmNvbSZndDssICZxdW90O3NpcGNvcmVAaWV0Zi5vcmcmcXVvdDsgJmx0O3NpcGNvcmVAaWV0Zi5v
cmcmZ3Q7LCAmcXVvdDtzaXBjb3JlLWNoYWlyc0BpZXRmLm9yZyZxdW90OyAmbHQ7c2lwY29yZS1j
aGFpcnNAaWV0Zi5vcmcmZ3Q7LCAmcXVvdDthZGFtQG5vc3RydW0uY29tJnF1b3Q7ICZsdDthZGFt
QG5vc3RydW0uY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6IDwvYj5SZTogW3NpcGNvcmVdIHJlZy1l
dmVudCBpc3N1ZSB3aXRoIG11bHRpLWlkZW50aXR5L211bHRpLWRldmljZTxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSB0aGluayBS
RkMgMzY4MCBpcyBkdWUgZm9yIHBheWxvYWQgc2NoZW1hIHVwZGF0ZS4gPG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbmUgdGhpbmcgdGhhdCBhbHdheXMgYm90
aGVyZWQgbWUgYWJvdXQgUkZDIDM2ODAgd2FzIHRoYXQgaXQgZG9lcyBub3QgZXhwb3NlIFJGQyAz
MzI3IFBhdGggaW5mb3JtYXRpb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPl9fX19fX19fX19fX188YnI+DQpS
b21hbiBTaHBvdW50PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPk9uIFR1ZSwgQXByIDIsIDIwMTkgYXQgNToyMyBBTSBDaHJpc3RlciBIb2xt
YmVyZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+
Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWJvdHRvbToxMi4wcHQiPkhpLDxicj4NCjxicj4NCkknZCBsaWtlIHRvIGFzayB0aGUgY2hh
aXJzIGFuZCBBRCBvbiBzb21lIGd1aWRhbmNlIG9uIGhvdyB0byBtb3ZlIGZvcndhcmQgd2l0aCB0
aGlzLiBUaGVyZSBzZWVtcyB0byBiZSBpbnRlcmVzdCBpbiB0aGUgaXNzdWUuPGJyPg0KPGJyPg0K
QXMgSSBoYXZlIGluZGljYXRlZCwgSSAqcGVyc29uYWxseSogdGhpbmsgdGhlIHJlYWwgcHJvYmxl
bSBpcyBkdXBsaWNhdGlvbiBvZiBkYXRhLCBzbyBzaW1wbHkgY29tcHJlc3NpbmcgaXQgZG9lcyBu
b3QgcmVhbGx5IHNvbHZlIHRoZSBwcm9ibGVtIGxvbmd0ZXJtLCBhbmQgdGhhdCBpcyB0aGUgaW5w
dXQgSSBoYXZlIHJlY2VpdmVkIGZyb20gb3RoZXJzIHRvby48YnI+DQo8YnI+DQpXZSBmb3Igc3Vy
ZSBuZWVkIHRvIHRha2UgT3V0Ym91bmQgKHJlYWQ6IHJlZy1pZCBhbmQgaW5zdGFuY2UtaWQpIGlu
dG8gY29uc2lkZXJhdGlvbi48YnI+DQo8YnI+DQpSZWdhcmRzLDxicj4NCjxicj4NCkNocmlzdGVy
PGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KT24gMjkvMDMvMjAxOSwgOS40NSwgJnF1b3Q7c2lwY29y
ZSBvbiBiZWhhbGYgb2YgQ2hyaXN0ZXIgSG9sbWJlcmcmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0
bzpzaXBjb3JlLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5zaXBjb3JlLWJvdW5j
ZXNAaWV0Zi5vcmc8L2E+IG9uIGJlaGFsZiBvZg0KPGEgaHJlZj0ibWFpbHRvOmNocmlzdGVyLmhv
bG1iZXJnQGVyaWNzc29uLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmNocmlzdGVyLmhvbG1iZXJnQGVy
aWNzc29uLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgSGkgRGFs
ZSw8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZndDtTbyBhbnkgc2NoZW1lIGZvciBhYnJpZGdp
bmcgcmVnaXN0cmF0aW9uIGV2ZW50cyBpcyBsaWtlbHkgdG8gaGF2ZSB0bzxicj4NCiZuYnNwOyAm
bmJzcDsgJmd0O2RlYWwgd2l0aCB1bmlxdWVzcyBpbiB0aGUgJmx0O3VyaSZndDsgYW5kICdpZCcg
c3RyaW5ncy48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7IE15IGFzc3VtcHRpb24gaXMgdGhhdCB0
aGUgJmx0O3VyaSZndDsgYW5kICdpZCcgYXJlIHVuaXF1ZSBmb3IgZWFjaCBjb250YWN0LiZuYnNw
OyAmbmJzcDsgPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5ic3A7ICZuYnNwOyBBIGJl
dHRlciB3YXkgdG8ganVkZ2UgdGhpcyBpcyB0byBsb29rIGF0IGEgKnJlYWwqIHJlZ2lzdHJhdGlv
biBldmVudCBmb3I8YnI+DQombmJzcDsgJm5ic3A7ICZndDsmbmJzcDsgJm5ic3A7IGEgc2l0dWF0
aW9uIGxpa2UgdGhpcyAtLSBzYXksIHRocmVlIFVBcyByZWdpc3RlcmVkIGZvciB0aGUgc2FtZSB0
aHJlZTxicj4NCiZuYnNwOyAmbmJzcDsgJmd0OyZuYnNwOyAmbmJzcDsgQU9Scy4mbmJzcDsgRG9l
cyBhbnlvbmUgaGF2ZSBhbnkgZXhhbXBsZXMgdG8gc2hhcmU/PGJyPg0KPGJyPg0KJm5ic3A7ICZu
YnNwOyBUaGUgZXhhbXBsZSBJIGdhdmUgd2FzIHJlZmxlY3RpbmcgYSByZWFsIGRlcGxveW1lbnQg
c2NlbmFyaW8uPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBSZWdhcmRzLDxicj4NCjxicj4NCiZu
YnNwOyAmbmJzcDsgQ2hyaXN0ZXI8YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
IE9uIDI5LzAzLzIwMTksIDMuNTUsICZxdW90O0RhbGUgUi4gV29ybGV5JnF1b3Q7ICZsdDs8YSBo
cmVmPSJtYWlsdG86d29ybGV5QGFyaWFkbmUuY29tIiB0YXJnZXQ9Il9ibGFuayI+d29ybGV5QGFy
aWFkbmUuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IFJvbWFuIFNocG91bnQgJmx0OzxhIGhyZWY9Im1haWx0bzpyb21hbkB0ZWx1cml4LmNv
bSIgdGFyZ2V0PSJfYmxhbmsiPnJvbWFuQHRlbHVyaXguY29tPC9hPiZndDsgd3JpdGVzOjxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmZ3Q7IFNob3VsZCBub3QgZWFjaCByZWdpc3Ry
YXRpb24gZW50cnkgaGF2ZSBhIGRpZmZlcmVudCBpbnN0YW5jZS1pZC9yZWctaWQ8YnI+DQombmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJmd0OyAoZGVmaW5lZCBpbiA8YSBocmVmPSJodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNTYyNiIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL3JmYzU2MjY8L2E+KSBpbiB1bmtub3duLXBhcmFtPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZndDsgYXR0cmlidXRlcz88YnI+DQo8YnI+DQombmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgTG9va2luZyBhdCB0aGUgZXhhbXBsZSBtb3JlIGNhcmVm
dWxseS4mbmJzcDsgVGhlIHR5cGljYWwgJmx0O3JlZ2lzdHJhdGlvbiZndDsgc3RhcnQ8YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgdGFnIGFuZCB0aGUgdHlwaWNhbCAmbHQ7Y29udGFj
dCZndDsgZWxlbWVudCBsb29rIGxpa2UgdGhpczo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJmx0O3RuczpyZWdpc3RyYXRpb24gaWQ9JnF1b3Q7MTIzNDU2Nzg5MCZxdW90
OyBhb3I9JnF1b3Q7c2lwOm1haWx0bzomIzQzOzxhIGhyZWY9Im1haWx0bzoxNTU1NjY2Nzc3N0Bp
bXMubW5jMDAxLm1jYzAwMS4zZ3BwbmV0d29ya3Mub3JnIiB0YXJnZXQ9Il9ibGFuayI+MTU1NTY2
Njc3NzdAaW1zLm1uYzAwMS5tY2MwMDEuM2dwcG5ldHdvcmtzLm9yZzwvYT4mcXVvdDsmZ3Q7PGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJmx0O3Ruczpjb250
YWN0IGV2ZW50PSZxdW90O3JlZ2lzdGVyZWQmcXVvdDsgaWQ9JnF1b3Q7MjM0NTY3ODkwMSZxdW90
OyBkdXJhdGlvbi1yZWdpc3RlcmVkPSZxdW90OzQyOTQ5NjcyOTUmcXVvdDs8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2Nz
ZXE9JnF1b3Q7NDI5NDk2NzI5NSZxdW90OyByZXRyeS1hZnRlcj0mcXVvdDs0Mjk0OTY3Mjk1JnF1
b3Q7IHE9JnF1b3Q7MCZxdW90OyBzdGF0ZT0mcXVvdDthY3RpdmUmcXVvdDs8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2Nh
bGxpZD0mcXVvdDtTdHJpbmcmcXVvdDsgZXhwaXJlcz0mcXVvdDs0Mjk0OTY3Mjk1JnF1b3Q7Jmd0
Ozxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bHQ7dG5zOnVyaSZndDtzaXA6JiM0MzsxNTU1NjY2Nzc3N0BbMjAwMTowZGI4Ojg1YTM6MDAwMDow
MDAwOjhhMmU6MDM3MDphYWFhXSZsdDsvdG5zOnVyaSZndDs8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJmx0O3RuczpkaXNwbGF5LW5hbWUgeG1s
Omxhbmc9JnF1b3Q7ZW4tdXMmcXVvdDsmZ3Q7U3RyaW5nJmx0Oy90bnM6ZGlzcGxheS1uYW1lJmd0
Ozxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bHQ7dG5zOnVua25vd24tcGFyYW0gbmFtZT0mcXVvdDtTdHJpbmcmcXVvdDsmZ3Q7U3RyaW5nJmx0
Oy90bnM6dW5rbm93bi1wYXJhbSZndDs8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbHQ7L3Ruczpjb250YWN0Jmd0Ozxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBBcyBJIHJlYWQgUkZDIDM2ODAsIHRoZSBpZCBhdHRyaWJ1dGUgb2Yg
Jmx0O3JlZ2lzdHJhdGlvbiZndDsgYW5kIHRoZSBpZDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBhdHRyaWJ1dGUgb2YgJmx0O2NvbnRhY3QmZ3Q7IGhhdmUgdG8gYmUgdW5pcXVlIHdp
dGhpbiB0aGUgJmx0O3JlZ2luZm8mZ3Q7Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBUaGUgYWN0dWFsIG5hbWUgb2YgdGhlIEFPUiBkaXNwbGF5ZWQgdG8gdGhlIHVzZXIg
b24gdGhlIGRldmljZSBpcyBsaWtlbHk8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
dG8gYmUgY3VzdG9taXplZCwgYnV0IEkgd2FzIHByb2JhYmx5IHdyb25nIHJlZ2FyZGluZyB0aGUg
Jmx0O2Rpc3BsYXktbmFtZSZndDs8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgZWxl
bWVudCBoZXJlIC0tIGl0J3MgdGFrZW4gZnJvbSB0aGUgQ29udGFjdCBoZWFkZXIgaW4gdGhlIFJF
R0lTVEVSPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHJlcXVlc3QsIGFuZCBtb3N0
IGxpa2VseSBpcyBlbXB0eS48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
VGhlIHNpcC5pbnN0YW5jZSBpbiB0aGUgQ29udGFjdCB3aWxsIHNob3cgdXAgYXMgYW4gJmx0O3Vu
a25vd24tcGFyYW0mZ3Q7PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGVsZW1lbnQs
IGJ1dCBpdCBzaG91bGQgYmUgdGhlIHNhbWUgZm9yIGFsbCAmbHQ7Y29udGFjdCZndDsgZWxlbWVu
dHMgZm9yPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHJlZ2lzdHJhdGlvbnMgZnJv
bSB0aGUgc2FtZSBVQS48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgVGhl
ICZsdDt1cmkmZ3Q7IGVsZW1lbnQgLS0gdGhlIGNvbnRhY3QgVVJJIC0tIGlzIGxpa2VseSB0byBj
b250YWluIGJvdGggc29tZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBwYXJ0IG9m
IHRoZSBBT1IgYW5kIHRoZSBJUCBhZGRyZXNzIG9mIHRoZSBVQSwgYW5kIHNvIHRoZXkncmUgbGlr
ZWx5IHRvPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJlIGRpZmZlcmVudCBmb3Ig
ZXZlcnkgJmx0O2NvbnRhY3QmZ3Q7IGVsZW1lbnQuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7IFNvIGFueSBzY2hlbWUgZm9yIGFicmlkZ2luZyByZWdpc3RyYXRpb24gZXZl
bnRzIGlzIGxpa2VseSB0byBoYXZlIHRvPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IGRlYWwgd2l0aCB1bmlxdWVzcyBpbiB0aGUgJmx0O3VyaSZndDsgYW5kICdpZCcgc3RyaW5ncy48
YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgQSBiZXR0ZXIgd2F5IHRvIGp1
ZGdlIHRoaXMgaXMgdG8gbG9vayBhdCBhICpyZWFsKiByZWdpc3RyYXRpb24gZXZlbnQgZm9yPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGEgc2l0dWF0aW9uIGxpa2UgdGhpcyAtLSBz
YXksIHRocmVlIFVBcyByZWdpc3RlcmVkIGZvciB0aGUgc2FtZSB0aHJlZTxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyBBT1JzLiZuYnNwOyBEb2VzIGFueW9uZSBoYXZlIGFueSBleGFt
cGxlcyB0byBzaGFyZT88YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgRGFs
ZTxicj4NCjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX188YnI+DQombmJzcDsgJm5ic3A7IHNpcGNvcmUgbWFpbGlu
ZyBsaXN0PGJyPg0KJm5ic3A7ICZuYnNwOyA8YSBocmVmPSJtYWlsdG86c2lwY29yZUBpZXRmLm9y
ZyIgdGFyZ2V0PSJfYmxhbmsiPnNpcGNvcmVAaWV0Zi5vcmc8L2E+PGJyPg0KJm5ic3A7ICZuYnNw
OyA8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcGNvcmUi
IHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Np
cGNvcmU8L2E+PGJyPg0KPGJyPg0KPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_0EAFEA5BB901417E812D1511ADA0F741ericssoncom_--


From nobody Tue Apr  2 12:13:21 2019
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCC6120075; Tue,  2 Apr 2019 12:13:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <sipcore-chairs@ietf.org>, <sipcore@ietf.org>, <draft-yusef-sipcore-digest-scheme@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155423239936.6278.1388625447167788779.idtracker@ietfa.amsl.com>
Date: Tue, 02 Apr 2019 12:13:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ykW0uOOAStyBv5VlrN5UhbunNc0>
Subject: [sipcore] The SIPCORE WG has placed draft-yusef-sipcore-digest-scheme in state "Call For Adoption By WG Issued"
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 19:13:20 -0000

The SIPCORE WG has placed draft-yusef-sipcore-digest-scheme in state
Call For Adoption By WG Issued (entered by Jean Mahoney)

The document is available at
https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/


From nobody Tue Apr  2 12:22:40 2019
Return-Path: <roman@telurix.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40B4C12023D for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 12:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
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 Ux6jWNdTtXH3 for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 12:22:36 -0700 (PDT)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 81C8312023B for <sipcore@ietf.org>; Tue,  2 Apr 2019 12:22:36 -0700 (PDT)
Received: by mail-pl1-x636.google.com with SMTP id t16so4872830plo.0 for <sipcore@ietf.org>; Tue, 02 Apr 2019 12:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OUjYDwYqp+cO+YsuOQYQ1AeIvCI+qNeSDGFl1NA/BvU=; b=N1fdtCEPIP9JH4EbiuIbd2Gk01wNx9xcxbsIwD13gcAqXRi+FRK2c5R/8mGpOXWhLg qLOUEjbBkJGDgKGcqCGlGofMeblXYxD55JkX1J5Z58T7ju1s1yV9bI8WpBRcLtBvCn+j HkZG5Hz5gvCu8Cbxwy3MpB2GAHk13VI31NPSe15J+i+aD53/Pvv0Cb/ssGcQHdEtiE+b 7gY0LNMDX4/tUc7aevzJmGtS1E4dv2g8LsLYpTM7RCTb0nt/QxPjcfKLYtlGek3/CX3z UEQ9FPmhtYJWwApHtHdcv9eMqtUi2/Bm/6YnBLLuwfmhMyXHs145qasoUMvof4v74Hnj OEVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OUjYDwYqp+cO+YsuOQYQ1AeIvCI+qNeSDGFl1NA/BvU=; b=ZmQSRS+H63JP82FqSQcYOFOLRzn9FuqKzJB7EKpIG9KNbVGUOJzduwshmpAMZ4bXC8 PKu7OCWIjmikv/Iw+nr677lBCazeFWAyZo6yQTWmgcFftISLxZ/gSPGed6mQ9TN+N53v 8iill7jBrsnza2q+hZlHlDyMNl+HsAcfcwVwbiqrSUL7m+R1uz99xEIa1vBR5eKXerWG 4iHelCYWehC91XWnsKG0tOB63ECjNZd2ppi+InB3m2TRAWhbKsYCGajnvgwxG3g0vijt bQzdOQS5jUHXZStwI/Zg1lhtJcX8i2NC6K4dKDWMzSfFhKGEcnclkS9gYnJyFwTT6l9h DeSw==
X-Gm-Message-State: APjAAAUUBMyw0nf5P7o1FZNnt3cr8BNXHAYwlCW9OowHEibx6Lj/aYpW BTO61I2EFPmW/F0FX8vVIAP5VVXSD7k=
X-Google-Smtp-Source: APXvYqzTxTp0ne6/1KbUWUPT236r6uloesy2q/Av4nHJ8m3560eetjtugtd/4PwrFzjMB+S1bSmvxw==
X-Received: by 2002:a17:902:e90b:: with SMTP id cs11mr13610163plb.243.1554232955537;  Tue, 02 Apr 2019 12:22:35 -0700 (PDT)
Received: from mail-pl1-f177.google.com (mail-pl1-f177.google.com. [209.85.214.177]) by smtp.gmail.com with ESMTPSA id g64sm32227106pfg.13.2019.04.02.12.22.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 12:22:34 -0700 (PDT)
Received: by mail-pl1-f177.google.com with SMTP id ck15so5557117plb.3; Tue, 02 Apr 2019 12:22:33 -0700 (PDT)
X-Received: by 2002:a17:902:7c8c:: with SMTP id y12mr53916582pll.209.1554232953608;  Tue, 02 Apr 2019 12:22:33 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5OKxs0PevSqthM5wp1=Q7OgrzuL71Gj=Y_tciKT7t7AVnNeA@mail.gmail.com> <8736n6la0k.fsf@hobgoblin.ariadne.com> <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com> <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com> <CAD5OKxsEdKD1x_A4Mc8kbMJ90cx63U2jd4EP+DmuCs9N87_swA@mail.gmail.com> <0EAFEA5B-B901-417E-812D-1511ADA0F741@ericsson.com>
In-Reply-To: <0EAFEA5B-B901-417E-812D-1511ADA0F741@ericsson.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 2 Apr 2019 15:22:24 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv6H=EDGBd2Yd0gE7aE7+_gQp2eTevrZS1Yw-jEnrLW0w@mail.gmail.com>
Message-ID: <CAD5OKxv6H=EDGBd2Yd0gE7aE7+_gQp2eTevrZS1Yw-jEnrLW0w@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>,  "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "adam@nostrum.com" <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="00000000000019225b0585910f7f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/uqIlUaVmgtEQ8Eho5zQOZAOIYQM>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 19:22:39 -0000

--00000000000019225b0585910f7f
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 2, 2019 at 2:45 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Just to clarify: if we want to change the schema, I think it should be
> done as a **new** schema. We should keep the old schema as it is, not to
> break existing deployments.
>
>
>
> So, we would have two schemas (the old one and the new one), and obviously
> the associated mechanisms to negotiate and indicate support of them.
>

I agree, but adding references within registration information imply new
schema and the mechanism to negotiate it. The typical solution would  be to
define a new MIME type for new schema version.

In general, I am not as much concerned with resulting schema size, but I
would like to make relationships between registrations and current use
cases, such as SIP Outbound, more obvious. For instance, if the same device
registers for the same AOR across multiple paths, the schema should reflect
this. In any case, I think RFC 3680 event schema is due for an update to
reflect current use cases, including one which result in high data
repetition.

Regards,
_____________
Roman Shpount

--00000000000019225b0585910f7f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail_sign=
ature" data-smartmail=3D"gmail_signature">On Tue, Apr 2, 2019 at 2:45 PM Ch=
rister Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">chris=
ter.holmberg@ericsson.com</a>&gt; wrote:<br></div></div></div><div class=3D=
"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"FI">
<div class=3D"gmail-m_1225775026610268786WordSection1">
<p class=3D"MsoNormal">Just to clarify: if we want to change the schema, I =
think it should be done as a *<b>new</b>* schema. We should keep the old sc=
hema as it is, not to break existing deployments.<br></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So, we would have two schemas (=
the old one and the new one), and obviously the associated mechanisms to ne=
gotiate and indicate support of them.</span></p></div></div></blockquote><d=
iv><br></div><div>I agree, but adding references within registration inform=
ation imply new schema and the mechanism to negotiate it. The typical solut=
ion would=C2=A0 be to define a new MIME type for new schema version.</div><=
div><br></div><div>In general, I am not as much concerned with resulting sc=
hema size, but I would like to make relationships between registrations and=
 current use cases, such as SIP Outbound, more obvious. For instance, if th=
e same device registers for the same AOR across multiple paths, the schema =
should reflect this. In any case, I think RFC 3680 event schema is due for =
an update to reflect current use cases, including one which result in high =
data repetition.</div><div><br></div><div>Regards,</div>_____________<br>Ro=
man Shpount<br class=3D"gmail-Apple-interchange-newline"><div>=C2=A0</div><=
/div></div>

--00000000000019225b0585910f7f--


From nobody Tue Apr  2 13:06:05 2019
Return-Path: <br@brianrosen.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC957120280 for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 13:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 JFvyN934T1gb for <sipcore@ietfa.amsl.com>; Tue,  2 Apr 2019 13:06:00 -0700 (PDT)
Received: from mail-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) (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 72B43120158 for <sipcore@ietf.org>; Tue,  2 Apr 2019 13:06:00 -0700 (PDT)
Received: by mail-qt1-x842.google.com with SMTP id d13so16829318qth.5 for <sipcore@ietf.org>; Tue, 02 Apr 2019 13:06:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=okrqhmOKsS2jhReu3sTAycH5h66YwLTcs2lmyT8KzPY=; b=b3Xg2+FEAcc7Ax5p45kLgICnY27Ivb6q5zuW126PPFaCW7499i28epQHUYO6kOh6tH 7ykhE9AOlkCCNrs6JCX9b/UZR+TzCghEkRLJcXi2ZH4+op2GowtW7lWH5XV9LlIvLIFL OPjl6boRtLQXYq681gKnCaa0+GUi+8/MSE42Ub7psoykmrH4t4ikVSEEb/NcZUeddiFP 5ie4h7mUq7ebKF/PCufjAtvGvexlw/shNlnpWO0uuDr7PZiD3m8YGCnZTjs/+J0RgQa6 0IaEiTyNlWg+6h0LGDaGM3KF6P5FHGDOkNY5cnkQ4Eljd0AW6tn2L6zUVIjRbPXBCmSD gEGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=okrqhmOKsS2jhReu3sTAycH5h66YwLTcs2lmyT8KzPY=; b=sm4Pl3rwugfQgsmrlzBUn+5xYQ6wHmMDwhHB6PRTblWsbP9fGwTBpCeYtkhb4MkMN8 jE3/Hfr0WesorfND/CfPIHV2ArdwRtOoUer1Bc8TlafG0Du2tah7PS/rrTA5oz1u8+Mv LYsJdcLO+YxyYI9tuH7vF5T1VXgSBNSbiBzWSGdpdfXa9cosVrf7CAt08TlxZ1SWJ0SR Mu5c7P28fb5ejZ6idoK0/UZEPBxkwORQniMbE9hWnJPrSJNONmTgTSi7OdzzUeK6Ia0m 87JwUsOCs4LUOjUQlgUeq00IB5xXNnB3/fNXf33GziQTRHKibuR7mDje8zAj/kzSWfio cneg==
X-Gm-Message-State: APjAAAVyVfrc1xBWNmSRYAdhshV06eiOnPNbSpuaY9n0rWw0WISw42VJ kyh3He9pN/g0ecYtL9Mn+aP85A==
X-Google-Smtp-Source: APXvYqz6Fr87LZqky/64Vq9Kzr+n/ux4Ts3RdWIDftyTckhukHNUg2buRZOeWtPB+vh4jjMPXe0YYQ==
X-Received: by 2002:ac8:2d02:: with SMTP id n2mr61205998qta.229.1554235559494;  Tue, 02 Apr 2019 13:05:59 -0700 (PDT)
Received: from brians-mbp-3.lan ([24.129.255.66]) by smtp.gmail.com with ESMTPSA id c9sm7683630qkb.86.2019.04.02.13.05.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 13:05:58 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com>
Date: Tue, 2 Apr 2019 16:05:57 -0400
Cc: "Dale R. Worley" <worley@ariadne.com>, Roman Shpount <roman@telurix.com>,  "sipcore@ietf.org" <sipcore@ietf.org>, "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "adam@nostrum.com" <adam@nostrum.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFC35E26-60BF-44A0-BB72-47DB0FD62FF0@brianrosen.net>
References: <CAD5OKxs0PevSqthM5wp1=Q7OgrzuL71Gj=Y_tciKT7t7AVnNeA@mail.gmail.com> <8736n6la0k.fsf@hobgoblin.ariadne.com> <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com> <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/C4UQtF9W-szbRYZWpCAIzXd6QjI>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 20:06:04 -0000

Write a draft!

We=E2=80=99re not very busy.

Brian

> On Apr 2, 2019, at 5:23 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> I'd like to ask the chairs and AD on some guidance on how to move =
forward with this. There seems to be interest in the issue.
>=20
> As I have indicated, I *personally* think the real problem is =
duplication of data, so simply compressing it does not really solve the =
problem longterm, and that is the input I have received from others too.
>=20
> We for sure need to take Outbound (read: reg-id and instance-id) into =
consideration.
>=20
> Regards,
>=20
> Christer
>=20
>=20
>=20
> =EF=BB=BFOn 29/03/2019, 9.45, "sipcore on behalf of Christer Holmberg" =
<sipcore-bounces@ietf.org on behalf of christer.holmberg@ericsson.com> =
wrote:
>=20
>    Hi Dale,
>=20
>> So any scheme for abridging registration events is likely to have to
>> deal with uniquess in the <uri> and 'id' strings.
>=20
>    My assumption is that the <uri> and 'id' are unique for each =
contact.   =20
>=20
>>   A better way to judge this is to look at a *real* registration =
event for
>>   a situation like this -- say, three UAs registered for the same =
three
>>   AORs.  Does anyone have any examples to share?
>=20
>    The example I gave was reflecting a real deployment scenario.
>=20
>    Regards,
>=20
>    Christer
>=20
>=20
>=20
>    On 29/03/2019, 3.55, "Dale R. Worley" <worley@ariadne.com> wrote:
>=20
>        Roman Shpount <roman@telurix.com> writes:
>> Should not each registration entry have a different =
instance-id/reg-id
>> (defined in https://tools.ietf.org/html/rfc5626) in unknown-param
>> attributes?
>=20
>        Looking at the example more carefully.  The typical =
<registration> start
>        tag and the typical <contact> element look like this:
>=20
>        <tns:registration id=3D"1234567890" =
aor=3D"sip:mailto:+15556667777@ims.mnc001.mcc001.3gppnetworks.org">
>            <tns:contact event=3D"registered" id=3D"2345678901" =
duration-registered=3D"4294967295"
>        	 cseq=3D"4294967295" retry-after=3D"4294967295" q=3D"0" =
state=3D"active"
>        	 callid=3D"String" expires=3D"4294967295">
>              =
<tns:uri>sip:+15556667777@[2001:0db8:85a3:0000:0000:8a2e:0370:aaaa]</tns:u=
ri>
>              <tns:display-name =
xml:lang=3D"en-us">String</tns:display-name>
>              <tns:unknown-param =
name=3D"String">String</tns:unknown-param>
>            </tns:contact>
>=20
>        As I read RFC 3680, the id attribute of <registration> and the =
id
>        attribute of <contact> have to be unique within the <reginfo>.
>=20
>        The actual name of the AOR displayed to the user on the device =
is likely
>        to be customized, but I was probably wrong regarding the =
<display-name>
>        element here -- it's taken from the Contact header in the =
REGISTER
>        request, and most likely is empty.
>=20
>        The sip.instance in the Contact will show up as an =
<unknown-param>
>        element, but it should be the same for all <contact> elements =
for
>        registrations from the same UA.
>=20
>        The <uri> element -- the contact URI -- is likely to contain =
both some
>        part of the AOR and the IP address of the UA, and so they're =
likely to
>        be different for every <contact> element.
>=20
>        So any scheme for abridging registration events is likely to =
have to
>        deal with uniquess in the <uri> and 'id' strings.
>=20
>        A better way to judge this is to look at a *real* registration =
event for
>        a situation like this -- say, three UAs registered for the same =
three
>        AORs.  Does anyone have any examples to share?
>=20
>        Dale
>=20
>=20
>    _______________________________________________
>    sipcore mailing list
>    sipcore@ietf.org
>    https://www.ietf.org/mailman/listinfo/sipcore
>=20
>=20


From nobody Tue Apr  2 14:39:28 2019
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31E3C120333; Tue,  2 Apr 2019 14:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 poAWer_ajBAd; Tue,  2 Apr 2019 14:39:23 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 A8AB812032E; Tue,  2 Apr 2019 14:39:16 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x32LdFOw088967 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 2 Apr 2019 16:39:15 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1554241156; bh=l6QFfF1d5Dqf2+bp0uRuRzd/ykBVAom66ND+GtSwNts=; h=To:From:Subject:Date; b=H/sHRQGHwsqn7WjXIrvVfNyCBwGVfWP/DunHfp30Oma2Y9RiP4uHwGTwpn2tHHX4f 8oqHeYLqmMGSkbclDOKKMXuZFw+JXKPJNzAQVKfwfbhISE0aMhSPmp7gHpjdfF013W tosySZs5ZA5xcW1arf7BIsDplvE8EvekxlJ5/fr0=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be mutabilis-2.local
To: draft-ietf-sipcore-rejected@ietf.org, SIPCORE <sipcore@ietf.org>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <2508d59d-e270-cfa4-e79c-d9da0f3c589c@nostrum.com>
Date: Tue, 2 Apr 2019 16:39:14 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ndojYpgCuMam79yonx-JToaDzAI>
Subject: [sipcore] Doc Shepherd review of draft-ietf-sipcore-rejected-05
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2019 21:39:27 -0000

Hi Eric and Bhavik,

Thanks for addressing all of the feedback so far. In preparation for the 
Doc Shepherd Write-up, I have run idnits, gone through the ID Checklist, 
and made my own pass through the draft. I have the following feedback 
below (overwhelmingly nits) -

Thanks!

Jean


------------------------------------------------------------------------
Major issues:
-------------

None.


Minor issues:
-------------

The Terminology section still needs a bit of tweaking (idnits complains):

In draft:

    This document uses the terms "MUST", "MUST NOT", "REQUIRED", "SHALL",
    "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
    "OPTIONAL" as described in BCP14 [RFC2119][RFC8174] when, and only
    when, they appear in all capitals, as shown here.


Current boilerplate:

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
    "OPTIONAL" in this document are to be interpreted as described in
    BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
    capitals, as shown here.


Nits:
-----

Throughout the document, replace "Call-Info header" with "Call-Info 
header field".


1. Introduction

Expand the acronym UAC on first use.

s/Figure 1 and Figure 2 shows/Figure 1 and Figure 2 show


Current:

                The problem here is that network elements downstream
    from the intermediary might interpret the 607 as a user (human)
    marking the call as unwanted, as opposed to a statistical, machine
    learning, vulnerable to the base rate fallacy [BaseRate] algorithm
    rejecting the call.  In other words, those downstream entities should
    not be relying on another entity 'deciding' the call is unwanted.


Suggested:

                The problem here is that network elements downstream
    from the intermediary might interpret the 607 as coming from a user
    (human) that has marked the call as unwanted, as opposed to coming
    from an algorithm using statistics or machine learning to reject
    the call. An algorithm can be vulnerable to the base rate fallacy
    [BaseRate]. In other words, those downstream entities should not rely
    on another entity 'deciding' the call is unwanted.


s/SIP header passed back/Call-Info header field passed back



3.3 UAC Operation

s/feature capability tag in the INVITE request/feature capability 
indicator in the Feature-Caps header field of the INVITE request



3.4 Legacy Interoperation

Current:

    One aspect of using a feature capability is only the network elements
    that will consume (UAC) or play an announcement (media gateway, SBC,
    or proxy) need understand the sip.608 feature capability.  All other
    (existing) infrastructure can remain without modification, assuming
    they are conformant to Section 16.6 of [RFC3261], specifically they
    will pass headers such as "Feature-Capability: sip.608" unmodified.

Suggested:

    One aspect of using a feature capability is that only the network
    elements that will either consume (UAC) or play an announcement
    (media gateway, session border controller (SBC) [RFC7092], or proxy)
    need to understand the sip.608 feature capability. The rest of the
    infrastructure does not need to be modified, assuming that the other
    network elements conform to Section 16.6 of [RFC3261], specifically
    that they will pass header fields such as "Feature-Capability:
    sip.608" unmodified.



3.5 Announcement Requirements

s/that will be doing the announcement/that handles the announcement

s/the modality for conveying/how to convey



4.1 Full Exchange

In the examples, follow guidance from RFC2606, RFC3849, and RFC6890 on 
constructing example addresses, FQDNs, and TNs:
    o Replace IPv4 addresses with addresses in the example space
      [RFC6890]: 192.0.2.0/24
      Or better yet, use IPv6 examples [RFC3849]: 2001:DB8::/32
    o Use example FQDNs specified in [RFC2606].
    o Use example phone numbers in the following space:
      +1<area code>555<0100-0199>


s/exemplary purposes/example purposes

s/at rest/at best



5.4. Call-Info Purpose

Current:

    This
    modifies the registry header field parameters and parameter values by
    adding this RFC as a reference to the line for the header field
    "Call-Info" and parameter name "purpose":

Suggested:

    This
    modifies the "Header Field Parameters and Parameter Values"
    subregistry of the "Session Initiation Protocol (SIP) Parameters"
    registry by adding this RFC as a reference to the line for the
    header field "Call-Info" and parameter name "purpose":



6. Security Considerations

Current:

    Another risk is for an attacker to purposely not include the sip.608
    feature capability in a flood of INVITE requests, direct those
    requests to proxies known to insert the sip.608 feature, and direct
    the SDP to a victim device.

Suggested:

    Another risk is for an attacker to flood a proxy that supports the
    sip.608 feature with INVITE requests that lack the sip.608 feature
    capability in order to direct the SDP to a victim's device.

s/pharming/phishing    (For more info on this edit, see RFC4949)

s/lookup/look up

s/dialled/dialed

s/jourisdiction's/jurisdiction's



8.3 Informative References

[BaseRate] s/ http://www.dtic.mil/get-tr-doc/pdf?AD=ADA045772 /
               https://apps.dtic.mil/docs/citations/ADA045772


From nobody Wed Apr  3 19:01:54 2019
Return-Path: <worley@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60EA1201DA for <sipcore@ietfa.amsl.com>; Wed,  3 Apr 2019 19:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 Ed_rNyCdFdLd for <sipcore@ietfa.amsl.com>; Wed,  3 Apr 2019 19:01:50 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 BA42D120397 for <sipcore@ietf.org>; Wed,  3 Apr 2019 19:01:50 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id BrVQhUeTWIaWtBrhNhuuMt; Thu, 04 Apr 2019 02:01:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1554343309; bh=XfeA6sw9VYe4qIGrNEDjhbWez48/icK0PF0ddaar7i8=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=Ah9Jzg2rhBOqLoc4zPou2pLTTrzUJGNn/2Gl4lb8QNbVQ5Zk6JzP7siTkJlfRro7x jymdNNzwTr4I1bf4Eu248zAC8LxNAkBgsv/1h8SotZxwMPtLNzFvw/qsVXSeBcSH49 np40MJ/lGI3Va1BPQEUAIT+21d68/1REkEAH3ppIeX87EJ4Wwyz+MJtFNVcQqYzHNR jjlG0q8P+wc+Sn6IDi4g+BMErf2V+FA/BMICWSZvfYxkfaDiCciqnT+M/7hkUKYbxk Oy0ymS1sw8Yc06J/GCbtXeV7Y5ci9SR51oHIk9mRcZKld32i9BKX8kNPGK9JQ2BnzF gSnuDaEzyXbug==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-17v.sys.comcast.net with ESMTPA id BrhMh1f50OJh2BrhNhIzXp; Thu, 04 Apr 2019 02:01:49 +0000
X-Xfinity-VMeta: sc=-100;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x3421lwp014297; Wed, 3 Apr 2019 22:01:47 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x3421lEU014294; Wed, 3 Apr 2019 22:01:47 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: roman@telurix.com, sipcore@ietf.org
In-Reply-To: <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com> (christer.holmberg@ericsson.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 03 Apr 2019 22:01:46 -0400
Message-ID: <87tvfeh6k5.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/CHsvVm1p3GYp2LZ0hHlt25oaE7A>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2019 02:01:53 -0000

Christer Holmberg <christer.holmberg@ericsson.com> writes:
> The example I gave was reflecting a real deployment scenario.

I tend to be dubious about something that "reflects" something else.
I'd much rather see a real example with whatever masking is necessary --
and an explanation of exactly what masking has been applied.

Dale


From nobody Wed Apr  3 19:30:14 2019
Return-Path: <worley@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B501201B6 for <sipcore@ietfa.amsl.com>; Wed,  3 Apr 2019 19:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 ru51e6UFVl-M for <sipcore@ietfa.amsl.com>; Wed,  3 Apr 2019 19:30:10 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 5BF3E1200F8 for <sipcore@ietf.org>; Wed,  3 Apr 2019 19:30:10 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id BrpChZey1XWW4Bs8nhMjCF; Thu, 04 Apr 2019 02:30:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1554345009; bh=jlI1cKLZ7ejmdMY8+B4JAf0Or9+cErCcn72gF4mNWxs=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=MKIKupfaCSaqw2ankvgV1TnQ+6wMpirEFFxsXkynP/aCfK1qTwjOQqooq/1POdESw pY83dxeqI7rTSqFirR+NasxOUCdRuY0UC4tJqYDpypUEvy4AQcAevnaJasr+jnmG0x N9FhbUNVgW6O9op04NeT+QbwEL8QHZY8OaapXbndmt8P2iLjwqil0vEyamYALA8mxR eLoWOyKjDFTx+3UcySXGciz6uqVy2v51LDxwzKlTBKR6Hb3iSjbbCGZjq8WP4SpUO/ q/KHif7mFhqhJxYAgsNS7ef7lad/6fDg78Jo6kX7MBvNnuY2O7DuxaX8gTLdKxm+Jp scgdaoMBEF7/w==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id Bs8lhozSyQ0wIBs8mhGFLV; Thu, 04 Apr 2019 02:30:09 +0000
X-Xfinity-VMeta: sc=0;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x342U7tq017683; Wed, 3 Apr 2019 22:30:07 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x342U6rT017671; Wed, 3 Apr 2019 22:30:06 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: mahoney@nostrum.com, sipcore@ietf.org
In-Reply-To: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com>
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 03 Apr 2019 22:30:06 -0400
Message-ID: <87pnq2h58x.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/wPszEwYLbJvcWliacI0O9M3C2dU>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2019 02:30:12 -0000

> On 01/04/2019, 23.46, A. Jean Mahoney wrote:
>     This is a call for adoption of draft-yusef-sipcore-digest-scheme in the 
>     SIPCORE working group.
>     
>     https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/

I favor adopting draft-yusef-sipcore-digest-scheme.

(Editorial:  The Abstract needs revision.  As far as I can tell, the
general idea is to have MD5 be replaced by SHA-256 in general usage.
But the specifics are that the document adds both SHA-256 and
SHA-512-256 and does not remove MD5.)

Dale


From nobody Fri Apr  5 06:09:02 2019
Return-Path: <rifaat.ietf@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27618120421 for <sipcore@ietfa.amsl.com>; Fri,  5 Apr 2019 06:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HqeOTlOqcAhR for <sipcore@ietfa.amsl.com>; Fri,  5 Apr 2019 06:08:59 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 91D121200EB for <sipcore@ietf.org>; Fri,  5 Apr 2019 06:08:59 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id v10so4901420iom.8 for <sipcore@ietf.org>; Fri, 05 Apr 2019 06:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sUBdgHY14QDv//ticHash8TzvwM4O6EXhDyovUxlPzI=; b=btvl8Gk44WtxG5aMFHp8gk9+Pnow4AgC/7l4qqZkA4+bYQVucyeHbaWtvQINj61UbL OLcbL873N5Jn2s8WHbFLaRBhipcxz0oXKMvjns1O/4usZkaBSZ5QBLbwZz9XDcpZNtY7 ZGjEVTVn5RVwGrdUtwf30utEIMyucxXhSuSqVJrut4oeeh74dB2/DdQlT0EULz87+xiA /k+ChifBaB2bt3JySRy3jgVA432Q4HmxVaRxrHpZg7KvLLcY4a8tujMv8++lUcGNwMei hbTl5+Q2uYwMJFBK2pYAUd7l2yModzC4yOYmTxNmQm5FWsyL69Yhmln9FSn5NZCU3x5O hCfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sUBdgHY14QDv//ticHash8TzvwM4O6EXhDyovUxlPzI=; b=ZiHDm+4QbPLwFjx1fUBPZ4nwLAQK7gcxm3ivx+m/rKJTD2CQNafwEkpbi6N8CRL5vB RpBNlcNHnAaPMBXzHD8pAdjrKUcMeeXRGhMl0TrIslqRlKVAVPdIXGLoKh6/i2rpHfar BtZtCT3HI0IZX0BtsIMSmj+acR25RvKq4GFXnEXyirP/kPyfkfO39ASH554z0aA9lTmX LyH6331OhSbw1mPUDOxa9myPt0HI0nOeQwrAMfIkhZ5KNV9WZFubD9jH19U6TG5wOiJ9 9eVmJ24P0XE08Y9lNh7FuWeztbcIpLaGpSTL8SG6kDJZk0Nu8+voeSkKmREYPNujWBlQ Fkww==
X-Gm-Message-State: APjAAAWpzvVO5SyGFW2ND6dGa3i2ZfMVsU6CmDDn4FQB4hJQO5VMMQMa /3CenqOn8Vc+vmZC7Ehd1NWWJNw6BcgXkqnKvXqJD2zr
X-Google-Smtp-Source: APXvYqysvtTCqDL2IK/caiMj7pyLwzMZRgJ5ht3LlhAeO/63KBoB2e0D7qKhtLiRf9Gb5TvmHb1O9WTnqMkad1saMII=
X-Received: by 2002:a6b:ed0c:: with SMTP id n12mr8291649iog.259.1554469738955;  Fri, 05 Apr 2019 06:08:58 -0700 (PDT)
MIME-Version: 1.0
References: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com> <87pnq2h58x.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87pnq2h58x.fsf@hobgoblin.ariadne.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Fri, 5 Apr 2019 09:08:47 -0400
Message-ID: <CAGL6epJwRMJpxO06GB5dSxfU=dqiXjkaW2ytgHOStt2t0d0ZQg@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: "A. Jean Mahoney" <mahoney@nostrum.com>, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009acb1d0585c830a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/WRZzjy-cd3WFFAWtzNS3LEBXgSk>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2019 13:09:01 -0000

--0000000000009acb1d0585c830a6
Content-Type: text/plain; charset="UTF-8"

Hi Dale,

The document does not require the removal of MD5 support because it is
needed for backward compatibility.

Regards,
 Rifaat



On Wed, Apr 3, 2019 at 10:30 PM Dale R. Worley <worley@ariadne.com> wrote:

> > On 01/04/2019, 23.46, A. Jean Mahoney wrote:
> >     This is a call for adoption of draft-yusef-sipcore-digest-scheme in
> the
> >     SIPCORE working group.
> >
> >     https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/
>
> I favor adopting draft-yusef-sipcore-digest-scheme.
>
> (Editorial:  The Abstract needs revision.  As far as I can tell, the
> general idea is to have MD5 be replaced by SHA-256 in general usage.
> But the specifics are that the document adds both SHA-256 and
> SHA-512-256 and does not remove MD5.)
>
> Dale
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

--0000000000009acb1d0585c830a6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Dale,<div><br></div><div>The document does not require =
the removal of MD5 support because it is needed for backward compatibility.=
</div><div><br></div><div>Regards,</div><div>=C2=A0Rifaat</div><div><br></d=
iv><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Wed, Apr 3, 2019 at 10:30 PM Dale R. Worley &lt;<a hre=
f=3D"mailto:worley@ariadne.com">worley@ariadne.com</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">&gt; On 01/04/2019, 23.46=
, A. Jean Mahoney wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0This is a call for adoption of draft-yusef-sipcore-=
digest-scheme in the <br>
&gt;=C2=A0 =C2=A0 =C2=A0SIPCORE working group.<br>
&gt;=C2=A0 =C2=A0 =C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-y=
usef-sipcore-digest-scheme/" rel=3D"noreferrer" target=3D"_blank">https://d=
atatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/</a><br>
<br>
I favor adopting draft-yusef-sipcore-digest-scheme.<br>
<br>
(Editorial:=C2=A0 The Abstract needs revision.=C2=A0 As far as I can tell, =
the<br>
general idea is to have MD5 be replaced by SHA-256 in general usage.<br>
But the specifics are that the document adds both SHA-256 and<br>
SHA-512-256 and does not remove MD5.)<br>
<br>
Dale<br>
<br>
_______________________________________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore</a><br>
</blockquote></div>

--0000000000009acb1d0585c830a6--


From nobody Fri Apr  5 06:11:09 2019
Return-Path: <rifaat.ietf@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0431203DA for <sipcore@ietfa.amsl.com>; Fri,  5 Apr 2019 06:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Hd7erogo-GFF for <sipcore@ietfa.amsl.com>; Fri,  5 Apr 2019 06:11:04 -0700 (PDT)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 8742B1200EB for <sipcore@ietf.org>; Fri,  5 Apr 2019 06:11:04 -0700 (PDT)
Received: by mail-it1-x135.google.com with SMTP id y10so9392767itc.1 for <sipcore@ietf.org>; Fri, 05 Apr 2019 06:11:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RgmiZZ7Kxvyj81lL4XPw2e9Sv2yTsZkLCriMwSrUWPo=; b=GjWez3or8nrUy5QOyRE4UZZzRk0D2A5aCqGD98ClyQffUNIoQRIrUmttiMLmyTMl0e vt7BNWIQBCD+WRoZ5xc216kM/958wT9LJmX94hfdMRe7ZuWNyhuAbF5ZEnjgKjbMucM8 HmvZi5eahdowNB/hUDOjuvi+VRLeBnldVU+JQDWGff+EH8GJ3++BtJK19io6zRMNYXLp M2y+QckcrKmRpBAYshb4EtnbYejduSuJ2TGFzMq4LEEJa3FT+rtDo0p4QMs9EOTE7hU+ Lq+0g6MXz+fzFnvxA7mLiiPwFc57QAeHrcky+BX/XKb4K5NlF2Zricn+6NdCla/AR1cV OnOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RgmiZZ7Kxvyj81lL4XPw2e9Sv2yTsZkLCriMwSrUWPo=; b=ngB0k1hSEkfioIzluEhrSPx+/cYRYiWVyxEJczNGKCCenyBtJ687LtonOrF7qoH43P jTaTaCrh//kMzaitE9+fXGb4E8KAHKIvGZY/m2kYeoUC7+acaRY3hhZkuUMY8L7BHLy/ ZMjp0LnrlExu8nBp4TgHpBP25jyay8NFZC9ebpdCdTq4HWh2HrIwN96uuhiE25a36ayW pdZEkrfvSZNQehb/HCeNQjOOmE1kJtneIqNB8qN4PTAFvc9u7WBW9858UHEd5woRV62U 86u7UzwK3DtX7/JjkCi0juciatJi7h8EFgbPklCL779W7RdiYE1ybufQNQF8Iz+1+4cU QOtw==
X-Gm-Message-State: APjAAAXweBxYIWHDokxwH+AWDKAZk0rDFYb7FWoBCdKdlOSNrr2mRUZs OptDaCwF+KUNM2wobkzHfM++FPs/L8duOEme1Mo=
X-Google-Smtp-Source: APXvYqwMF7lEB1f2S1C6rxrq8t/G0nwKxzvDA8nsq4l2F6mtyhirxVvBpdeNv9nIlv7uzn3wqpV1CkTTLD02+hhF5/Y=
X-Received: by 2002:a02:b60b:: with SMTP id h11mr9377489jam.125.1554469863909;  Fri, 05 Apr 2019 06:11:03 -0700 (PDT)
MIME-Version: 1.0
References: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com> <F6F9524E-B17C-47DC-8C6D-B7A87FDFF007@ericsson.com> <1BBA9452-9798-4E98-BBB9-9EC308BA4106@brianrosen.net>
In-Reply-To: <1BBA9452-9798-4E98-BBB9-9EC308BA4106@brianrosen.net>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Fri, 5 Apr 2019 09:10:53 -0400
Message-ID: <CAGL6ep+EwO0WyimGUsPcOgiKSwtJyy8m1XZAr89Mc-cN6s2p+A@mail.gmail.com>
To: Brian Rosen <br@brianrosen.net>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000d6d7a0585c83851"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/2M1QgnbUkcsKA8P8lW6Taq5qKvw>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2019 13:11:07 -0000

--0000000000000d6d7a0585c83851
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Brian,

I have one comment about that in the IANA section.
If that is not enough, I can add one more sentence to make it clear that
this is the intent.

Regards,
 Rifaat


On Tue, Apr 2, 2019 at 10:35 AM Brian Rosen <br@brianrosen.net> wrote:

> <As individual>
> I support adopting this draft, and the NENA folks need it.  I wonder if w=
e
> should expressly allow any new entries to the RFC7616 registry to be used=
.
>
> Brian
>
> > On Apr 2, 2019, at 2:35 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
> >
> > Hi,
> >
> > I support the adopting the draft, and I will provide input (I think the
> draft is in pretty good shape already) and review the document.
> >
> > Regards,
> >
> > Christer
> >
> >
> > =EF=BB=BFOn 01/04/2019, 23.46, "sipcore on behalf of A. Jean Mahoney" <
> sipcore-bounces@ietf.org on behalf of mahoney@nostrum.com> wrote:
> >
> >    Hi all,
> >
> >    This is a call for adoption of draft-yusef-sipcore-digest-scheme in
> the
> >    SIPCORE working group.
> >
> >    https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/
> >
> >    Please send your comments to the list or to the chairs by April 15th=
.
> >
> >    Thanks!
> >
> >    Jean
> >
> >    _______________________________________________
> >    sipcore mailing list
> >    sipcore@ietf.org
> >    https://www.ietf.org/mailman/listinfo/sipcore
> >
> >
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

--0000000000000d6d7a0585c83851
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi=C2=A0Brian,<div><br></div><div>I have one comment about=
 that in the IANA section.</div><div>If that is not enough, I can add one m=
ore sentence to make it clear that this is the intent.</div><div><br></div>=
<div>Regards,</div><div>=C2=A0Rifaat</div><div><br></div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Apr 2, 201=
9 at 10:35 AM Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net">br@brian=
rosen.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">&lt;As individual&gt;<br>
I support adopting this draft, and the NENA folks need it.=C2=A0 I wonder i=
f we should expressly allow any new entries to the RFC7616 registry to be u=
sed.<br>
<br>
Brian<br>
<br>
&gt; On Apr 2, 2019, at 2:35 AM, Christer Holmberg &lt;<a href=3D"mailto:ch=
rister.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.=
com</a>&gt; wrote:<br>
&gt; <br>
&gt; Hi,<br>
&gt; <br>
&gt; I support the adopting the draft, and I will provide input (I think th=
e draft is in pretty good shape already) and review the document.<br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Christer<br>
&gt; <br>
&gt; <br>
&gt; =EF=BB=BFOn 01/04/2019, 23.46, &quot;sipcore on behalf of A. Jean Maho=
ney&quot; &lt;<a href=3D"mailto:sipcore-bounces@ietf.org" target=3D"_blank"=
>sipcore-bounces@ietf.org</a> on behalf of <a href=3D"mailto:mahoney@nostru=
m.com" target=3D"_blank">mahoney@nostrum.com</a>&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Hi all,<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 This is a call for adoption of draft-yusef-sipcore-digest=
-scheme in the <br>
&gt;=C2=A0 =C2=A0 SIPCORE working group.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 <a href=3D"https://datatracker.ietf.org/doc/draft-yusef-s=
ipcore-digest-scheme/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/</a><br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Please send your comments to the list or to the chairs by=
 April 15th.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Thanks!<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Jean<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 _______________________________________________<br>
&gt;=C2=A0 =C2=A0 sipcore mailing list<br>
&gt;=C2=A0 =C2=A0 <a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sip=
core@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/sipcore"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/sipcore</a><br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; sipcore mailing list<br>
&gt; <a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore</a><=
br>
<br>
_______________________________________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore</a><br>
</blockquote></div>

--0000000000000d6d7a0585c83851--


From nobody Fri Apr  5 11:09:13 2019
Return-Path: <br@brianrosen.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 894E312024F for <sipcore@ietfa.amsl.com>; Fri,  5 Apr 2019 11:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 MA0GKlw2YZQH for <sipcore@ietfa.amsl.com>; Fri,  5 Apr 2019 11:08:53 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 ACDB712051E for <sipcore@ietf.org>; Fri,  5 Apr 2019 11:08:52 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id k14so8494836qtb.0 for <sipcore@ietf.org>; Fri, 05 Apr 2019 11:08:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=HXfMdcmrTp1HKFA3Iz1qcwd4/OyUUJB18Qx/f0Fop1E=; b=Al3U+m39DUsdn0lzvEyMD6LIzRYpmdy/3rkcor09cDjiErk3wk2sMR6Tn9DODusqcR HQd1Hv/SITsumfxVTD+VG3xtGnDbO9/l6aknsHL1uBHhZREkHJ2WrI5ucv/ctbWv+jxZ tRYkarimnnyuk+WnYYUf+m4nh9Ih6i3fTCEjBSB3D5hwTYSSayei5G7cq3BikZStJwPG kwdiNaVJ1XXecunEjISPDonsthkAs1iyeZDAKrRU8zCTolPTp7FfRVn/P20ve+1k8R9w XZePKeXqqVbTWVW/0mrgFYjwy2dDqteMETdmkYgM7oo/FX7++Gsv51EtPmwfv4Nz125P UU8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=HXfMdcmrTp1HKFA3Iz1qcwd4/OyUUJB18Qx/f0Fop1E=; b=SPZdmt91QNksrC7x677rTVynS42VcD4km0O+9LJtxYyoW0y+IEwdlb1bxrn4oqK2sY ymnddvkMEXNHCIcNfKgx48kYtVPKVaI5txo/pIMbazw07RR5Fp05BDhP63lha3PluSXq Frh/HTpUvg5KASLHAUkHVu7s53puqtHjQTyhgxh7bcJ2IygmbQqaO+UIoqJRKPI6Dm/i /uTagWx52s8fu7V3pCYx4rVmZbLln75Jkdh6HVkzrC4TAn/OXHXpX0fktsUs1vqQ615V 4MdJU1hl8TPAERaoe5klIPYTFpQvEVBzYUFA73B2rjNs8JnqJpJcaf6OBunGdDTccCvY SmZA==
X-Gm-Message-State: APjAAAX8B4sWiB/aErpovZIAved3rvW+FKCy8GiLivDqJDpMsuVIvLig IsRbcIKaNqFE+11fh09Cbcc6LEJQgI4=
X-Google-Smtp-Source: APXvYqyYZeIrmkKU/ZbIcDV/ykGa7GeJK9j3Wt7ZCOnWzX7BU4i+PIU2ipjqEHkO1cbm7qtuPtOA8A==
X-Received: by 2002:ac8:1833:: with SMTP id q48mr12278403qtj.133.1554487731642;  Fri, 05 Apr 2019 11:08:51 -0700 (PDT)
Received: from brians-mbp-3.lan ([24.129.255.66]) by smtp.gmail.com with ESMTPSA id o37sm12037253qte.55.2019.04.05.11.08.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Apr 2019 11:08:51 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <7F5A8856-4127-45FC-ACD9-6AF191535774@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4F4E3376-0BA5-4D1D-8602-710C4C8E2EB9"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 5 Apr 2019 14:08:49 -0400
In-Reply-To: <CAGL6epJwRMJpxO06GB5dSxfU=dqiXjkaW2ytgHOStt2t0d0ZQg@mail.gmail.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, SIPCORE <sipcore@ietf.org>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
References: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com> <87pnq2h58x.fsf@hobgoblin.ariadne.com> <CAGL6epJwRMJpxO06GB5dSxfU=dqiXjkaW2ytgHOStt2t0d0ZQg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/V1Ef3mDDDhzHJkvnbX3FXfbYEjk>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2019 18:09:00 -0000

--Apple-Mail=_4F4E3376-0BA5-4D1D-8602-710C4C8E2EB9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

<as individual>
Consider adding text saying that MD5 is not deprecated by this document =
but its use is restricted to older devices and when communicating with =
newer devices SHA MUST be used.

Brian

> On Apr 5, 2019, at 9:08 AM, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> =
wrote:
>=20
> Hi Dale,
>=20
> The document does not require the removal of MD5 support because it is =
needed for backward compatibility.
>=20
> Regards,
>  Rifaat
>=20
>=20
>=20
> On Wed, Apr 3, 2019 at 10:30 PM Dale R. Worley <worley@ariadne.com =
<mailto:worley@ariadne.com>> wrote:
> > On 01/04/2019, 23.46, A. Jean Mahoney wrote:
> >     This is a call for adoption of draft-yusef-sipcore-digest-scheme =
in the=20
> >     SIPCORE working group.
> >    =20
> >     =
https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/ =
<https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/>
>=20
> I favor adopting draft-yusef-sipcore-digest-scheme.
>=20
> (Editorial:  The Abstract needs revision.  As far as I can tell, the
> general idea is to have MD5 be replaced by SHA-256 in general usage.
> But the specifics are that the document adds both SHA-256 and
> SHA-512-256 and does not remove MD5.)
>=20
> Dale
>=20
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org <mailto:sipcore@ietf.org>
> https://www.ietf.org/mailman/listinfo/sipcore =
<https://www.ietf.org/mailman/listinfo/sipcore>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore


--Apple-Mail=_4F4E3376-0BA5-4D1D-8602-710C4C8E2EB9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">&lt;as individual&gt;<div class=3D"">Consider adding text =
saying that MD5 is not deprecated by this document but its use is =
restricted to older devices and when communicating with newer devices =
SHA MUST be used.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Brian<br class=3D""><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Apr =
5, 2019, at 9:08 AM, Rifaat Shekh-Yusef &lt;<a =
href=3D"mailto:rifaat.ietf@gmail.com" =
class=3D"">rifaat.ietf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">Hi Dale,<div class=3D""><br class=3D""></div><div =
class=3D"">The document does not require the removal of MD5 support =
because it is needed for backward compatibility.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regards,</div><div =
class=3D"">&nbsp;Rifaat</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr =
3, 2019 at 10:30 PM Dale R. Worley &lt;<a =
href=3D"mailto:worley@ariadne.com" class=3D"">worley@ariadne.com</a>&gt; =
wrote:<br class=3D""></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">&gt; On 01/04/2019, 23.46, A. Jean =
Mahoney wrote:<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;This is a call for adoption of =
draft-yusef-sipcore-digest-scheme in the <br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;SIPCORE working group.<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme=
/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-sch=
eme/</a><br class=3D"">
<br class=3D"">
I favor adopting draft-yusef-sipcore-digest-scheme.<br class=3D"">
<br class=3D"">
(Editorial:&nbsp; The Abstract needs revision.&nbsp; As far as I can =
tell, the<br class=3D"">
general idea is to have MD5 be replaced by SHA-256 in general usage.<br =
class=3D"">
But the specifics are that the document adds both SHA-256 and<br =
class=3D"">
SHA-512-256 and does not remove MD5.)<br class=3D"">
<br class=3D"">
Dale<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
sipcore mailing list<br class=3D"">
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank" =
class=3D"">sipcore@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/sipcore</a><br =
class=3D"">
</blockquote></div>
_______________________________________________<br class=3D"">sipcore =
mailing list<br class=3D""><a href=3D"mailto:sipcore@ietf.org" =
class=3D"">sipcore@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/sipcore<br =
class=3D""></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_4F4E3376-0BA5-4D1D-8602-710C4C8E2EB9--


From nobody Sat Apr  6 11:32:04 2019
Return-Path: <rifaat.ietf@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D518212007C for <sipcore@ietfa.amsl.com>; Sat,  6 Apr 2019 11:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9gpcqFLalJEL for <sipcore@ietfa.amsl.com>; Sat,  6 Apr 2019 11:32:01 -0700 (PDT)
Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 0669E12007A for <sipcore@ietf.org>; Sat,  6 Apr 2019 11:32:01 -0700 (PDT)
Received: by mail-it1-x12c.google.com with SMTP id 139so14828822ita.4 for <sipcore@ietf.org>; Sat, 06 Apr 2019 11:32:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FjuBQDCyB1G7Vkv1yXPufVJE+2sLLoDFZDb/Pmt26Lg=; b=F/gJpLoaP7opK9Ergkz+WK1JLg01Mq5Rub6OVO3IA7dSGgnWIhubevMD4l9wfBWAXM 572dsZX9pz33mYyMSYZ60tSUmP6VYWk2BMLS1uQZW0AMJwFVbtXGqkpl5qlY5R1oLP3d rM2gKkYVn8sjWxpzigjoZcgPMSlsqu3niutOeibZXOdcEW+rJyFX8fUNxariU20E3wB1 95PIzPs63zob7OLQKUVRCDgZ5wcsWqJnQATvyUmYSgkQ4Flnu1b0gvz4M7gjEXijr+yp SykMvvIWmXbJBvb+IeuDLtVHP524YZkXJCmbpq/mAveTcpHZIie5TjjGch3icRuS3dee Q75A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FjuBQDCyB1G7Vkv1yXPufVJE+2sLLoDFZDb/Pmt26Lg=; b=hbQc6kLG6MEKLicKFKmsyySAUK18isOBOUJ01cStl0zHfl8LJ/9CfOC2Rr9i3CUow2 FxBOyZlEdXgQ4x0mxIazMxPMyJRD9rKz6/QHyZBxQSD56c4cVXNgn+p+ryQzAsGciFPW t9qZ+PX/U4nEtJihHdQ9h2Bm/QAHZFuZ4q9yho2KP7InoyAdeQC6lDKLoPIwJcGJ+3FN kTpq0PLib8kdWuxr88uxihspy/767nvUZJ/TYbPb2BelBApau8LUeRw7/1f0dPSzcg3V 6DYTVeQs9Qkr+MH99lGVWWgKJMJcYvt+BkFWrAMMOV7ZyBw161kUBP7GyGtGOeq5pug8 RF2w==
X-Gm-Message-State: APjAAAWds7ajaHUDBj++ePP8WbCVc0D0Z0awGzhsIKlog4V+RL73LLnI aIsOsqFjOrg76Bk2HvyMkh2HnBVODVouapgpW8I=
X-Google-Smtp-Source: APXvYqwpFP/z8odj7T0BxogbmWtcXLf2tDzEylTHmCN2vkE1gmK+6jEbGSXwNCWfPsfur13Q6QkUymsQF8LunPF5ffM=
X-Received: by 2002:a24:4e82:: with SMTP id r124mr13905173ita.34.1554575520398;  Sat, 06 Apr 2019 11:32:00 -0700 (PDT)
MIME-Version: 1.0
References: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com> <87pnq2h58x.fsf@hobgoblin.ariadne.com> <CAGL6epJwRMJpxO06GB5dSxfU=dqiXjkaW2ytgHOStt2t0d0ZQg@mail.gmail.com> <7F5A8856-4127-45FC-ACD9-6AF191535774@brianrosen.net>
In-Reply-To: <7F5A8856-4127-45FC-ACD9-6AF191535774@brianrosen.net>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Sat, 6 Apr 2019 14:31:49 -0400
Message-ID: <CAGL6ep+nFHPdW819kZRgL-2Q=yVdRDy0UYgQdBZRQ8D-TwG8vw@mail.gmail.com>
To: Brian Rosen <br@brianrosen.net>
Cc: "Dale R. Worley" <worley@ariadne.com>, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ab83ab0585e0d1a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/wX1HEQPVVoFzigFpok5X1REwrf4>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2019 18:32:03 -0000

--000000000000ab83ab0585e0d1a3
Content-Type: text/plain; charset="UTF-8"

It will be very difficult to enforce this, as a downgrade attack will
always be possible unless a secure mechanism to identify the client is
being used.
I will add some text to cover this.

Regards,
 Rifaat


On Fri, Apr 5, 2019 at 2:08 PM Brian Rosen <br@brianrosen.net> wrote:

> <as individual>
> Consider adding text saying that MD5 is not deprecated by this document
> but its use is restricted to older devices and when communicating with
> newer devices SHA MUST be used.
>
> Brian
>
> On Apr 5, 2019, at 9:08 AM, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
> wrote:
>
> Hi Dale,
>
> The document does not require the removal of MD5 support because it is
> needed for backward compatibility.
>
> Regards,
>  Rifaat
>
>
>
> On Wed, Apr 3, 2019 at 10:30 PM Dale R. Worley <worley@ariadne.com> wrote:
>
>> > On 01/04/2019, 23.46, A. Jean Mahoney wrote:
>> >     This is a call for adoption of draft-yusef-sipcore-digest-scheme in
>> the
>> >     SIPCORE working group.
>> >
>> >     https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/
>>
>> I favor adopting draft-yusef-sipcore-digest-scheme.
>>
>> (Editorial:  The Abstract needs revision.  As far as I can tell, the
>> general idea is to have MD5 be replaced by SHA-256 in general usage.
>> But the specifics are that the document adds both SHA-256 and
>> SHA-512-256 and does not remove MD5.)
>>
>> Dale
>>
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
>>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>
>
>

--000000000000ab83ab0585e0d1a3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It will be very difficult to enforce this, as a downgrade =
attack will always be possible unless a secure mechanism to identify the cl=
ient is being used.<div>I will add some text to cover this.</div><div><br><=
/div><div>Regards,</div><div>=C2=A0Rifaat</div><div><br></div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Apr 5=
, 2019 at 2:08 PM Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net">br@b=
rianrosen.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div style=3D"overflow-wrap: break-word;">&lt;as individual&gt=
;<div>Consider adding text saying that MD5 is not deprecated by this docume=
nt but its use is restricted to older devices and when communicating with n=
ewer devices SHA MUST be used.</div><div><br></div><div>Brian<br><div><div>=
<br><blockquote type=3D"cite"><div>On Apr 5, 2019, at 9:08 AM, Rifaat Shekh=
-Yusef &lt;<a href=3D"mailto:rifaat.ietf@gmail.com" target=3D"_blank">rifaa=
t.ietf@gmail.com</a>&gt; wrote:</div><br class=3D"gmail-m_30743177745384005=
25Apple-interchange-newline"><div><div dir=3D"ltr">Hi Dale,<div><br></div><=
div>The document does not require the removal of MD5 support because it is =
needed for backward compatibility.</div><div><br></div><div>Regards,</div><=
div>=C2=A0Rifaat</div><div><br></div><div><br></div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr 3, 2019 at =
10:30 PM Dale R. Worley &lt;<a href=3D"mailto:worley@ariadne.com" target=3D=
"_blank">worley@ariadne.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">&gt; On 01/04/2019, 23.46, A. Jean Mahoney wrote=
:<br>
&gt;=C2=A0 =C2=A0 =C2=A0This is a call for adoption of draft-yusef-sipcore-=
digest-scheme in the <br>
&gt;=C2=A0 =C2=A0 =C2=A0SIPCORE working group.<br>
&gt;=C2=A0 =C2=A0 =C2=A0<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-y=
usef-sipcore-digest-scheme/" rel=3D"noreferrer" target=3D"_blank">https://d=
atatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/</a><br>
<br>
I favor adopting draft-yusef-sipcore-digest-scheme.<br>
<br>
(Editorial:=C2=A0 The Abstract needs revision.=C2=A0 As far as I can tell, =
the<br>
general idea is to have MD5 be replaced by SHA-256 in general usage.<br>
But the specifics are that the document adds both SHA-256 and<br>
SHA-512-256 and does not remove MD5.)<br>
<br>
Dale<br>
<br>
_______________________________________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore</a><br>
</blockquote></div>
_______________________________________________<br>sipcore mailing list<br>=
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br><a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/sipcore</a><br></div></blockquote=
></div><br></div></div></div></blockquote></div>

--000000000000ab83ab0585e0d1a3--


From nobody Sun Apr  7 12:32:57 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D9121204B0; Sun,  7 Apr 2019 12:32:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <155466557638.18165.16593484046255854518@ietfa.amsl.com>
Date: Sun, 07 Apr 2019 12:32:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/NGOQYxYrwjactdKtauRldmHXf0Q>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-rejected-06.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2019 19:32:57 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Protocol Core WG of the IETF.

        Title           : A Session Initiation Protocol (SIP) Response Code for Rejected Calls
        Authors         : Eric W. Burger
                          Bhavik Nagda
	Filename        : draft-ietf-sipcore-rejected-06.txt
	Pages           : 22
	Date            : 2019-04-07

Abstract:
   This document defines the 608 (Rejected) SIP response code.  This
   response code enables calling parties to learn that an intermediary
   rejected their call attempt.  The call will not be answered.  As a
   6xx code, the caller will be aware that future attempts to contact
   the same UAS will likely fail.  The present use case driving the need
   for the 608 response code is when the intermediary is an analytics
   engine.  In this case, the rejection is by a machine or other
   process.  This contrasts with the 607 (Unwanted) SIP response code,
   which a human at the target UAS indicated the call was not wanted.
   In some jurisdictions this distinction is important.  This document
   also defines the use of the Call-Info header field in 608 responses
   to enable rejected callers to contact entities that blocked their
   calls in error.  This provides a remediation mechanism for legal
   callers that find their calls blocked.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-rejected/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-sipcore-rejected-06
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-rejected-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-rejected-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Apr  7 12:36:01 2019
Return-Path: <eburger@standardstrack.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8D81204B0 for <sipcore@ietfa.amsl.com>; Sun,  7 Apr 2019 12:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.689
X-Spam-Level: 
X-Spam-Status: No, score=-1.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.com
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 HiEYw-eb3Qjk for <sipcore@ietfa.amsl.com>; Sun,  7 Apr 2019 12:35:59 -0700 (PDT)
Received: from biz221.inmotionhosting.com (biz221.inmotionhosting.com [198.46.93.79]) (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 4466D12033D for <sipcore@ietf.org>; Sun,  7 Apr 2019 12:35:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=um8HzDiAxO5Qdb7rbywtYOd5WiMEF9tq7Wur1Qv805E=; b=IWGO+J2MBog9uk/y4Tfoexpfm c1uF3Kn0pHoE85xZM+grKocMGqK8PgsxMDF5NRRGcGCdS3e8rM8oV5jKXbyFnjW/FQq3FfMHSUCWw z2D7m7uGm+BhShFdxf34CcXGU81FmBF9WgVuFstXwWlDaDeGtVA2FUFrlU/AAbSMQZqIs=;
Received: from [68.100.196.217] (port=55730 helo=[192.168.10.26]) by biz221.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <eburger@standardstrack.com>) id 1hDDZy-0000nm-Tt; Sun, 07 Apr 2019 12:35:58 -0700
From: Eric Burger <eburger@standardstrack.com>
Message-Id: <F08720C2-2DB7-4F45-BF5C-E253D5B84619@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BE44B972-7488-48E7-B8CB-617F9A41EEAE"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Sun, 7 Apr 2019 15:35:45 -0400
In-Reply-To: <2508d59d-e270-cfa4-e79c-d9da0f3c589c@nostrum.com>
Cc: SIPCORE <sipcore@ietf.org>
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <2508d59d-e270-cfa4-e79c-d9da0f3c589c@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.8)
X-OutGoing-Spam-Status: No, score=0.3
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz221.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/XAYQpX_EQUhePszlvyagFbP3liI>
Subject: Re: [sipcore] Doc Shepherd review of draft-ietf-sipcore-rejected-05
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2019 19:36:01 -0000

--Apple-Mail=_BE44B972-7488-48E7-B8CB-617F9A41EEAE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Updates have been done. I could not tell you who did the updates because =
now it has been passivized ;-)

The only update not applied is that while it is best to protect the key, =
it really needs to be protected at rest.


> On Apr 2, 2019, at 5:39 PM, A. Jean Mahoney <mahoney@nostrum.com> =
wrote:
>=20
> Hi Eric and Bhavik,
>=20
> Thanks for addressing all of the feedback so far. In preparation for =
the Doc Shepherd Write-up, I have run idnits, gone through the ID =
Checklist, and made my own pass through the draft. I have the following =
feedback below (overwhelmingly nits) -
>=20
> Thanks!
>=20
> Jean
>=20
>=20
> =
------------------------------------------------------------------------
> Major issues:
> -------------
>=20
> None.
>=20
>=20
> Minor issues:
> -------------
>=20
> The Terminology section still needs a bit of tweaking (idnits =
complains):
>=20
> In draft:
>=20
>   This document uses the terms "MUST", "MUST NOT", "REQUIRED", =
"SHALL",
>   "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
>   "OPTIONAL" as described in BCP14 [RFC2119][RFC8174] when, and only
>   when, they appear in all capitals, as shown here.
>=20
>=20
> Current boilerplate:
>=20
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>   "OPTIONAL" in this document are to be interpreted as described in
>   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
>   capitals, as shown here.
>=20
>=20
> Nits:
> -----
>=20
> Throughout the document, replace "Call-Info header" with "Call-Info =
header field".
>=20
>=20
> 1. Introduction
>=20
> Expand the acronym UAC on first use.
>=20
> s/Figure 1 and Figure 2 shows/Figure 1 and Figure 2 show
>=20
>=20
> Current:
>=20
>               The problem here is that network elements downstream
>   from the intermediary might interpret the 607 as a user (human)
>   marking the call as unwanted, as opposed to a statistical, machine
>   learning, vulnerable to the base rate fallacy [BaseRate] algorithm
>   rejecting the call.  In other words, those downstream entities =
should
>   not be relying on another entity 'deciding' the call is unwanted.
>=20
>=20
> Suggested:
>=20
>               The problem here is that network elements downstream
>   from the intermediary might interpret the 607 as coming from a user
>   (human) that has marked the call as unwanted, as opposed to coming
>   from an algorithm using statistics or machine learning to reject
>   the call. An algorithm can be vulnerable to the base rate fallacy
>   [BaseRate]. In other words, those downstream entities should not =
rely
>   on another entity 'deciding' the call is unwanted.
>=20
>=20
> s/SIP header passed back/Call-Info header field passed back
>=20
>=20
>=20
> 3.3 UAC Operation
>=20
> s/feature capability tag in the INVITE request/feature capability =
indicator in the Feature-Caps header field of the INVITE request
>=20
>=20
>=20
> 3.4 Legacy Interoperation
>=20
> Current:
>=20
>   One aspect of using a feature capability is only the network =
elements
>   that will consume (UAC) or play an announcement (media gateway, SBC,
>   or proxy) need understand the sip.608 feature capability.  All other
>   (existing) infrastructure can remain without modification, assuming
>   they are conformant to Section 16.6 of [RFC3261], specifically they
>   will pass headers such as "Feature-Capability: sip.608" unmodified.
>=20
> Suggested:
>=20
>   One aspect of using a feature capability is that only the network
>   elements that will either consume (UAC) or play an announcement
>   (media gateway, session border controller (SBC) [RFC7092], or proxy)
>   need to understand the sip.608 feature capability. The rest of the
>   infrastructure does not need to be modified, assuming that the other
>   network elements conform to Section 16.6 of [RFC3261], specifically
>   that they will pass header fields such as "Feature-Capability:
>   sip.608" unmodified.
>=20
>=20
>=20
> 3.5 Announcement Requirements
>=20
> s/that will be doing the announcement/that handles the announcement
>=20
> s/the modality for conveying/how to convey
>=20
>=20
>=20
> 4.1 Full Exchange
>=20
> In the examples, follow guidance from RFC2606, RFC3849, and RFC6890 on =
constructing example addresses, FQDNs, and TNs:
>   o Replace IPv4 addresses with addresses in the example space
>     [RFC6890]: 192.0.2.0/24
>     Or better yet, use IPv6 examples [RFC3849]: 2001:DB8::/32
>   o Use example FQDNs specified in [RFC2606].
>   o Use example phone numbers in the following space:
>     +1<area code>555<0100-0199>
>=20
>=20
> s/exemplary purposes/example purposes
>=20
> s/at rest/at best
>=20
>=20
>=20
> 5.4. Call-Info Purpose
>=20
> Current:
>=20
>   This
>   modifies the registry header field parameters and parameter values =
by
>   adding this RFC as a reference to the line for the header field
>   "Call-Info" and parameter name "purpose":
>=20
> Suggested:
>=20
>   This
>   modifies the "Header Field Parameters and Parameter Values"
>   subregistry of the "Session Initiation Protocol (SIP) Parameters"
>   registry by adding this RFC as a reference to the line for the
>   header field "Call-Info" and parameter name "purpose":
>=20
>=20
>=20
> 6. Security Considerations
>=20
> Current:
>=20
>   Another risk is for an attacker to purposely not include the sip.608
>   feature capability in a flood of INVITE requests, direct those
>   requests to proxies known to insert the sip.608 feature, and direct
>   the SDP to a victim device.
>=20
> Suggested:
>=20
>   Another risk is for an attacker to flood a proxy that supports the
>   sip.608 feature with INVITE requests that lack the sip.608 feature
>   capability in order to direct the SDP to a victim's device.
>=20
> s/pharming/phishing    (For more info on this edit, see RFC4949)
>=20
> s/lookup/look up
>=20
> s/dialled/dialed
>=20
> s/jourisdiction's/jurisdiction's
>=20
>=20
>=20
> 8.3 Informative References
>=20
> [BaseRate] s/ http://www.dtic.mil/get-tr-doc/pdf?AD=3DADA045772 /
>              https://apps.dtic.mil/docs/citations/ADA045772
>=20
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore


--Apple-Mail=_BE44B972-7488-48E7-B8CB-617F9A41EEAE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIzBAEBCAAdFiEEfEc/N7T7IfiAuDEHDDCGh758rskFAlyqUREACgkQDDCGh758
rsmzDQ/+Pk3lvpuEP//s4F4QK04N31Sni4qBxwHOqpS3UgigquZo0KwzDNQ99JYO
PKczWDXluTb4gBclswPyrD/kanEBjlWIBFyBN0ADB95v/w6V3n0houhjyOvAJsaD
xJBN8ZHg1iDOmkvd/n2TqMlhnmyrVb+zMLTbYnGVm6sgQJ1abmGtX1QU9WKFvvIA
lf4+q10L/Q5dge6o2E9bDG2PnAills5AgMmYWYFIpvgWqZcJW3dktIf3VBDnX4id
jkSVYfCbIkPqvyOStx0MM4Dv+Gl42Yl+Veb9mhW5cdv59XXYFLC1qjOKrgCpl0kD
5BSCb/UXjWPzW72iiOSXI2mgxYrkgS5YgUxHXU6FJ7sH9BjYE9pUnRqUJEvo6Bim
im7cQhJWNpjwXDpMKOjD3pm4UbaYqEEgxkdxw6+nWzZNTN9XurzEKU2Ez3rmy0+b
4F5qwp0906BtUxaUcL2upJaomoNiojUTmgDPCHzMPJIRMtN/fE7ltiOvyovWsx34
pl4NvFSjNFuQ1rwNOn+ipZH7bHBV+xqYzMaGTmaNTzpI6BdDNS2oth75HNRLOBTH
eZZUXgcHtd2Z3AWO0LYyrOMMGILGy4sd+dYE5DnkANRilkwu2ZXi+FtmJ7kOIEQ8
MB/pP+QAXTDHZWWHgEwaYjErkoMfAFS6DD1PTXZGjvJBIoF9+Jo=
=Py4f
-----END PGP SIGNATURE-----

--Apple-Mail=_BE44B972-7488-48E7-B8CB-617F9A41EEAE--


From nobody Mon Apr  8 15:16:37 2019
Return-Path: <noreply@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6375120362; Mon,  8 Apr 2019 15:16:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney via Datatracker <noreply@ietf.org>
To: <adam@nostrum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: Jean Mahoney <mahoney@nostrum.com>, sipcore@ietf.org, iesg-secretary@ietf.org, mahoney@nostrum.com, sipcore-chairs@ietf.org
Message-ID: <155476179585.30155.13326904406933535790.idtracker@ietfa.amsl.com>
Date: Mon, 08 Apr 2019 15:16:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/LzTaFsP5tbs3wKx3k8PWDgLYMEQ>
Subject: [sipcore] Publication has been requested for draft-ietf-sipcore-rejected-06
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 22:16:36 -0000

Jean Mahoney has requested publication of draft-ietf-sipcore-rejected-06 as Proposed Standard on behalf of the SIPCORE working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-sipcore-rejected/


From nobody Mon Apr  8 15:18:08 2019
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9BF120684 for <sipcore@ietfa.amsl.com>; Mon,  8 Apr 2019 15:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 QoTDKEPtIE1U for <sipcore@ietfa.amsl.com>; Mon,  8 Apr 2019 15:17:56 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 2345D120687 for <sipcore@ietf.org>; Mon,  8 Apr 2019 15:17:56 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x38MHsm4096158 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 8 Apr 2019 17:17:55 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1554761875; bh=IcXidcUp/zpwp4HV5jyR+vsao/k76grTFo4UXqmbjYs=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=PIcRNIHyGJnerKV6EIWpzEzNmiJwsAyf3yahwxciFVXPx1piUGKn43uYlir/WJvGD 9BXEbnbQbAed3Sa5mlsjIq5mdbiv9N23W5J273kkMnfXkfW4TQJjsmvCyn1/z7p+Js 4UXEauRcOwpPTff18Q/Dq4TaqM5Dde5KX3uZUhuQ=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be mutabilis-2.local
To: Eric Burger <eburger@standardstrack.com>
Cc: SIPCORE <sipcore@ietf.org>
References: <2508d59d-e270-cfa4-e79c-d9da0f3c589c@nostrum.com> <F08720C2-2DB7-4F45-BF5C-E253D5B84619@standardstrack.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <258a1ac5-579b-7078-ab78-8a7c375e205a@nostrum.com>
Date: Mon, 8 Apr 2019 17:17:54 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <F08720C2-2DB7-4F45-BF5C-E253D5B84619@standardstrack.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/j11abwOe5NzEOO_vbOSaBXcNUcA>
Subject: Re: [sipcore] Doc Shepherd review of draft-ietf-sipcore-rejected-05
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 22:18:07 -0000

Hi Eric,

Thanks given ;-)

I've completed the Document Shepherd write-up: 
https://datatracker.ietf.org/doc/draft-ietf-sipcore-rejected/shepherdwriteup/

And have requested publication. Next step will be for the AD to review.

Jean

On 4/7/19 2:35 PM, Eric Burger wrote:
> Updates have been done. I could not tell you who did the updates because now it has been passivized ;-)
> 
> The only update not applied is that while it is best to protect the key, it really needs to be protected at rest.
> 
> 
>> On Apr 2, 2019, at 5:39 PM, A. Jean Mahoney <mahoney@nostrum.com> wrote:
>>
>> Hi Eric and Bhavik,
>>
>> Thanks for addressing all of the feedback so far. In preparation for the Doc Shepherd Write-up, I have run idnits, gone through the ID Checklist, and made my own pass through the draft. I have the following feedback below (overwhelmingly nits) -
>>
>> Thanks!
>>
>> Jean
>>
>>
>> ------------------------------------------------------------------------
>> Major issues:
>> -------------
>>
>> None.
>>
>>
>> Minor issues:
>> -------------
>>
>> The Terminology section still needs a bit of tweaking (idnits complains):
>>
>> In draft:
>>
>>    This document uses the terms "MUST", "MUST NOT", "REQUIRED", "SHALL",
>>    "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
>>    "OPTIONAL" as described in BCP14 [RFC2119][RFC8174] when, and only
>>    when, they appear in all capitals, as shown here.
>>
>>
>> Current boilerplate:
>>
>>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>>    "OPTIONAL" in this document are to be interpreted as described in
>>    BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
>>    capitals, as shown here.
>>
>>
>> Nits:
>> -----
>>
>> Throughout the document, replace "Call-Info header" with "Call-Info header field".
>>
>>
>> 1. Introduction
>>
>> Expand the acronym UAC on first use.
>>
>> s/Figure 1 and Figure 2 shows/Figure 1 and Figure 2 show
>>
>>
>> Current:
>>
>>                The problem here is that network elements downstream
>>    from the intermediary might interpret the 607 as a user (human)
>>    marking the call as unwanted, as opposed to a statistical, machine
>>    learning, vulnerable to the base rate fallacy [BaseRate] algorithm
>>    rejecting the call.  In other words, those downstream entities should
>>    not be relying on another entity 'deciding' the call is unwanted.
>>
>>
>> Suggested:
>>
>>                The problem here is that network elements downstream
>>    from the intermediary might interpret the 607 as coming from a user
>>    (human) that has marked the call as unwanted, as opposed to coming
>>    from an algorithm using statistics or machine learning to reject
>>    the call. An algorithm can be vulnerable to the base rate fallacy
>>    [BaseRate]. In other words, those downstream entities should not rely
>>    on another entity 'deciding' the call is unwanted.
>>
>>
>> s/SIP header passed back/Call-Info header field passed back
>>
>>
>>
>> 3.3 UAC Operation
>>
>> s/feature capability tag in the INVITE request/feature capability indicator in the Feature-Caps header field of the INVITE request
>>
>>
>>
>> 3.4 Legacy Interoperation
>>
>> Current:
>>
>>    One aspect of using a feature capability is only the network elements
>>    that will consume (UAC) or play an announcement (media gateway, SBC,
>>    or proxy) need understand the sip.608 feature capability.  All other
>>    (existing) infrastructure can remain without modification, assuming
>>    they are conformant to Section 16.6 of [RFC3261], specifically they
>>    will pass headers such as "Feature-Capability: sip.608" unmodified.
>>
>> Suggested:
>>
>>    One aspect of using a feature capability is that only the network
>>    elements that will either consume (UAC) or play an announcement
>>    (media gateway, session border controller (SBC) [RFC7092], or proxy)
>>    need to understand the sip.608 feature capability. The rest of the
>>    infrastructure does not need to be modified, assuming that the other
>>    network elements conform to Section 16.6 of [RFC3261], specifically
>>    that they will pass header fields such as "Feature-Capability:
>>    sip.608" unmodified.
>>
>>
>>
>> 3.5 Announcement Requirements
>>
>> s/that will be doing the announcement/that handles the announcement
>>
>> s/the modality for conveying/how to convey
>>
>>
>>
>> 4.1 Full Exchange
>>
>> In the examples, follow guidance from RFC2606, RFC3849, and RFC6890 on constructing example addresses, FQDNs, and TNs:
>>    o Replace IPv4 addresses with addresses in the example space
>>      [RFC6890]: 192.0.2.0/24
>>      Or better yet, use IPv6 examples [RFC3849]: 2001:DB8::/32
>>    o Use example FQDNs specified in [RFC2606].
>>    o Use example phone numbers in the following space:
>>      +1<area code>555<0100-0199>
>>
>>
>> s/exemplary purposes/example purposes
>>
>> s/at rest/at best
>>
>>
>>
>> 5.4. Call-Info Purpose
>>
>> Current:
>>
>>    This
>>    modifies the registry header field parameters and parameter values by
>>    adding this RFC as a reference to the line for the header field
>>    "Call-Info" and parameter name "purpose":
>>
>> Suggested:
>>
>>    This
>>    modifies the "Header Field Parameters and Parameter Values"
>>    subregistry of the "Session Initiation Protocol (SIP) Parameters"
>>    registry by adding this RFC as a reference to the line for the
>>    header field "Call-Info" and parameter name "purpose":
>>
>>
>>
>> 6. Security Considerations
>>
>> Current:
>>
>>    Another risk is for an attacker to purposely not include the sip.608
>>    feature capability in a flood of INVITE requests, direct those
>>    requests to proxies known to insert the sip.608 feature, and direct
>>    the SDP to a victim device.
>>
>> Suggested:
>>
>>    Another risk is for an attacker to flood a proxy that supports the
>>    sip.608 feature with INVITE requests that lack the sip.608 feature
>>    capability in order to direct the SDP to a victim's device.
>>
>> s/pharming/phishing    (For more info on this edit, see RFC4949)
>>
>> s/lookup/look up
>>
>> s/dialled/dialed
>>
>> s/jourisdiction's/jurisdiction's
>>
>>
>>
>> 8.3 Informative References
>>
>> [BaseRate] s/ http://www.dtic.mil/get-tr-doc/pdf?AD=ADA045772 /
>>               https://apps.dtic.mil/docs/citations/ADA045772
>>
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
> 


From nobody Mon Apr  8 23:19:49 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D8112075C; Mon,  8 Apr 2019 23:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 UzIDL7Wlpc8e; Mon,  8 Apr 2019 23:19:44 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130041.outbound.protection.outlook.com [40.107.13.41]) (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 122B812075A; Mon,  8 Apr 2019 23:19:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pU+ClEeKZcKZ1L7WBHQjP78lpy3V0mpOkcbwfnSHJZI=; b=Dm2eUHgEGcBxbf2EVkSJ4Q34SU/XQhXysKFL6Ia+++BkfXGjDFo/LZdcMr1EV7ApZUqAATSO+C9gC2MbyqBGTIp1Ro6agNuzASbnSn1fH6hS3eToXG/G97BMhDvrv4q8XdspkNB6x145Am+jfvby3D7sTv4+pEWYq/bPErYj7dE=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.8; Tue, 9 Apr 2019 06:19:39 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::a832:85f:a8bb:73b9%5]) with mapi id 15.20.1792.007; Tue, 9 Apr 2019 06:19:39 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian Rosen <br@brianrosen.net>
CC: "Dale R. Worley" <worley@ariadne.com>, Roman Shpount <roman@telurix.com>,  "sipcore@ietf.org" <sipcore@ietf.org>, "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, "adam@nostrum.com" <adam@nostrum.com>
Thread-Topic: [sipcore] reg-event issue with multi-identity/multi-device
Thread-Index: AQHU5dKIZHWL8hDqjUW2JMDFs9lEoaYiXI0AgAZ1boCAAIFXgIAKS74A
Date: Tue, 9 Apr 2019 06:19:39 +0000
Message-ID: <C9A8031C-098C-4675-B1E7-3764B6E6F953@ericsson.com>
References: <CAD5OKxs0PevSqthM5wp1=Q7OgrzuL71Gj=Y_tciKT7t7AVnNeA@mail.gmail.com> <8736n6la0k.fsf@hobgoblin.ariadne.com> <24A3CCD0-F4C9-439F-8A2B-9BA52E071D52@ericsson.com> <B7FDF46A-2263-4FF5-A386-4AA5195DD34A@ericsson.com> <FFC35E26-60BF-44A0-BB72-47DB0FD62FF0@brianrosen.net>
In-Reply-To: <FFC35E26-60BF-44A0-BB72-47DB0FD62FF0@brianrosen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 02fa3646-0681-4ac7-0d2d-08d6bcb358f9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR07MB3161; 
x-ms-traffictypediagnostic: HE1PR07MB3161:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <HE1PR07MB3161C2D8D67671D7DD37F76E932D0@HE1PR07MB3161.eurprd07.prod.outlook.com>
x-forefront-prvs: 000227DA0C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(346002)(396003)(39860400002)(136003)(189003)(199004)(2906002)(36756003)(54906003)(476003)(81156014)(44832011)(33656002)(2616005)(66066001)(71190400001)(53936002)(229853002)(6512007)(86362001)(83716004)(102836004)(6246003)(14444005)(11346002)(6306002)(8676002)(6916009)(478600001)(71200400001)(966005)(58126008)(316002)(6506007)(4326008)(6486002)(93886005)(305945005)(14454004)(3846002)(99286004)(68736007)(256004)(6436002)(6116002)(81166006)(7736002)(486006)(26005)(106356001)(97736004)(82746002)(186003)(105586002)(8936002)(76176011)(5660300002)(53546011)(25786009)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3161; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 0QdOGp7RBHHu9yeYRtCfx8bNsLcMCcuEjx0nmcAK20W4wv5+Thb+EZlS0DvPAHPBR9tbxZ2Cj+KGM/TBCwC+LEvh9EPTFvo16MkeBM7S51EDIygasmd3WLXUTtgt2QMmwgStyVkK86r8vDYrYc11JQaf0BG3VHhUlCVkJfukGxyjBymwUoOk44puUk2biiAgn4Swrel35p4fVGF/0qWsqZGhXYd5gMh5Kvxo2AQAJtKnnVQdStjWhJ+3woFgQNM/sk+5UrNt/Z7Wh0LNjTzkhMzaGk3DzHe6fe0HtRQuJrAKQWWScZV3BQfBwm1KP1FHm5+uPiKHPCuHvnEaj0JSX7QCBO2Ke+8Ohn5rdZ9UbOgTdoHF8DmlpfUfcYfCJDeyiI94HhqvQ7pq+6JOun/DBfGhSkOYcvueVEDYxLK8ryU=
Content-Type: text/plain; charset="utf-8"
Content-ID: <37268C97002D144DA1615860B8F0D78C@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 02fa3646-0681-4ac7-0d2d-08d6bcb358f9
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Apr 2019 06:19:39.6447 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3161
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/AVHz-kmDCcFyUuFCJb1egW4gjuI>
Subject: Re: [sipcore] reg-event issue with multi-identity/multi-device
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2019 06:19:47 -0000

SGksDQoNCkknbSBoYXBweSB0byBwdXQgc29tZXRoaW5nIHRvZ2V0aGVyIHJlZ2FyZGluZyB0aGUg
ZHVwbGljYXRpb24gaXNzdWUuDQoNCkknbSBhbHNvIGhhcHB5IHRvIGNvdmVyIE91dGJvdW5kLCBi
dXQgYXQgdGhlIG1vbWVudCBJIGRvbid0IGhhdmUgYSBzdWdnZXN0aW9uIG9uIGhvdy93aGF0L2lm
IG1vZGlmaWNhdGlvbnMgYXJlIG5lZWRlZC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQrv
u79PbiAwMi8wNC8yMDE5LCAyMy4wNiwgIkJyaWFuIFJvc2VuIiA8YnJAYnJpYW5yb3Nlbi5uZXQ+
IHdyb3RlOg0KDQogICAgV3JpdGUgYSBkcmFmdCENCiAgICANCiAgICBXZeKAmXJlIG5vdCB2ZXJ5
IGJ1c3kuDQogICAgDQogICAgQnJpYW4NCiAgICANCiAgICA+IE9uIEFwciAyLCAyMDE5LCBhdCA1
OjIzIEFNLCBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29t
PiB3cm90ZToNCiAgICA+IA0KICAgID4gSGksDQogICAgPiANCiAgICA+IEknZCBsaWtlIHRvIGFz
ayB0aGUgY2hhaXJzIGFuZCBBRCBvbiBzb21lIGd1aWRhbmNlIG9uIGhvdyB0byBtb3ZlIGZvcndh
cmQgd2l0aCB0aGlzLiBUaGVyZSBzZWVtcyB0byBiZSBpbnRlcmVzdCBpbiB0aGUgaXNzdWUuDQog
ICAgPiANCiAgICA+IEFzIEkgaGF2ZSBpbmRpY2F0ZWQsIEkgKnBlcnNvbmFsbHkqIHRoaW5rIHRo
ZSByZWFsIHByb2JsZW0gaXMgZHVwbGljYXRpb24gb2YgZGF0YSwgc28gc2ltcGx5IGNvbXByZXNz
aW5nIGl0IGRvZXMgbm90IHJlYWxseSBzb2x2ZSB0aGUgcHJvYmxlbSBsb25ndGVybSwgYW5kIHRo
YXQgaXMgdGhlIGlucHV0IEkgaGF2ZSByZWNlaXZlZCBmcm9tIG90aGVycyB0b28uDQogICAgPiAN
CiAgICA+IFdlIGZvciBzdXJlIG5lZWQgdG8gdGFrZSBPdXRib3VuZCAocmVhZDogcmVnLWlkIGFu
ZCBpbnN0YW5jZS1pZCkgaW50byBjb25zaWRlcmF0aW9uLg0KICAgID4gDQogICAgPiBSZWdhcmRz
LA0KICAgID4gDQogICAgPiBDaHJpc3Rlcg0KICAgID4gDQogICAgPiANCiAgICA+IA0KICAgID4g
T24gMjkvMDMvMjAxOSwgOS40NSwgInNpcGNvcmUgb24gYmVoYWxmIG9mIENocmlzdGVyIEhvbG1i
ZXJnIiA8c2lwY29yZS1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBjaHJpc3Rlci5ob2xt
YmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KICAgID4gDQogICAgPiAgICBIaSBEYWxlLA0KICAg
ID4gDQogICAgPj4gU28gYW55IHNjaGVtZSBmb3IgYWJyaWRnaW5nIHJlZ2lzdHJhdGlvbiBldmVu
dHMgaXMgbGlrZWx5IHRvIGhhdmUgdG8NCiAgICA+PiBkZWFsIHdpdGggdW5pcXVlc3MgaW4gdGhl
IDx1cmk+IGFuZCAnaWQnIHN0cmluZ3MuDQogICAgPiANCiAgICA+ICAgIE15IGFzc3VtcHRpb24g
aXMgdGhhdCB0aGUgPHVyaT4gYW5kICdpZCcgYXJlIHVuaXF1ZSBmb3IgZWFjaCBjb250YWN0LiAg
ICANCiAgICA+IA0KICAgID4+ICAgQSBiZXR0ZXIgd2F5IHRvIGp1ZGdlIHRoaXMgaXMgdG8gbG9v
ayBhdCBhICpyZWFsKiByZWdpc3RyYXRpb24gZXZlbnQgZm9yDQogICAgPj4gICBhIHNpdHVhdGlv
biBsaWtlIHRoaXMgLS0gc2F5LCB0aHJlZSBVQXMgcmVnaXN0ZXJlZCBmb3IgdGhlIHNhbWUgdGhy
ZWUNCiAgICA+PiAgIEFPUnMuICBEb2VzIGFueW9uZSBoYXZlIGFueSBleGFtcGxlcyB0byBzaGFy
ZT8NCiAgICA+IA0KICAgID4gICAgVGhlIGV4YW1wbGUgSSBnYXZlIHdhcyByZWZsZWN0aW5nIGEg
cmVhbCBkZXBsb3ltZW50IHNjZW5hcmlvLg0KICAgID4gDQogICAgPiAgICBSZWdhcmRzLA0KICAg
ID4gDQogICAgPiAgICBDaHJpc3Rlcg0KICAgID4gDQogICAgPiANCiAgICA+IA0KICAgID4gICAg
T24gMjkvMDMvMjAxOSwgMy41NSwgIkRhbGUgUi4gV29ybGV5IiA8d29ybGV5QGFyaWFkbmUuY29t
PiB3cm90ZToNCiAgICA+IA0KICAgID4gICAgICAgIFJvbWFuIFNocG91bnQgPHJvbWFuQHRlbHVy
aXguY29tPiB3cml0ZXM6DQogICAgPj4gU2hvdWxkIG5vdCBlYWNoIHJlZ2lzdHJhdGlvbiBlbnRy
eSBoYXZlIGEgZGlmZmVyZW50IGluc3RhbmNlLWlkL3JlZy1pZA0KICAgID4+IChkZWZpbmVkIGlu
IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1NjI2KSBpbiB1bmtub3duLXBhcmFtDQog
ICAgPj4gYXR0cmlidXRlcz8NCiAgICA+IA0KICAgID4gICAgICAgIExvb2tpbmcgYXQgdGhlIGV4
YW1wbGUgbW9yZSBjYXJlZnVsbHkuICBUaGUgdHlwaWNhbCA8cmVnaXN0cmF0aW9uPiBzdGFydA0K
ICAgID4gICAgICAgIHRhZyBhbmQgdGhlIHR5cGljYWwgPGNvbnRhY3Q+IGVsZW1lbnQgbG9vayBs
aWtlIHRoaXM6DQogICAgPiANCiAgICA+ICAgICAgICA8dG5zOnJlZ2lzdHJhdGlvbiBpZD0iMTIz
NDU2Nzg5MCIgYW9yPSJzaXA6bWFpbHRvOisxNTU1NjY2Nzc3N0BpbXMubW5jMDAxLm1jYzAwMS4z
Z3BwbmV0d29ya3Mub3JnIj4NCiAgICA+ICAgICAgICAgICAgPHRuczpjb250YWN0IGV2ZW50PSJy
ZWdpc3RlcmVkIiBpZD0iMjM0NTY3ODkwMSIgZHVyYXRpb24tcmVnaXN0ZXJlZD0iNDI5NDk2NzI5
NSINCiAgICA+ICAgICAgICAJIGNzZXE9IjQyOTQ5NjcyOTUiIHJldHJ5LWFmdGVyPSI0Mjk0OTY3
Mjk1IiBxPSIwIiBzdGF0ZT0iYWN0aXZlIg0KICAgID4gICAgICAgIAkgY2FsbGlkPSJTdHJpbmci
IGV4cGlyZXM9IjQyOTQ5NjcyOTUiPg0KICAgID4gICAgICAgICAgICAgIDx0bnM6dXJpPnNpcDor
MTU1NTY2Njc3NzdAWzIwMDE6MGRiODo4NWEzOjAwMDA6MDAwMDo4YTJlOjAzNzA6YWFhYV08L3Ru
czp1cmk+DQogICAgPiAgICAgICAgICAgICAgPHRuczpkaXNwbGF5LW5hbWUgeG1sOmxhbmc9ImVu
LXVzIj5TdHJpbmc8L3RuczpkaXNwbGF5LW5hbWU+DQogICAgPiAgICAgICAgICAgICAgPHRuczp1
bmtub3duLXBhcmFtIG5hbWU9IlN0cmluZyI+U3RyaW5nPC90bnM6dW5rbm93bi1wYXJhbT4NCiAg
ICA+ICAgICAgICAgICAgPC90bnM6Y29udGFjdD4NCiAgICA+IA0KICAgID4gICAgICAgIEFzIEkg
cmVhZCBSRkMgMzY4MCwgdGhlIGlkIGF0dHJpYnV0ZSBvZiA8cmVnaXN0cmF0aW9uPiBhbmQgdGhl
IGlkDQogICAgPiAgICAgICAgYXR0cmlidXRlIG9mIDxjb250YWN0PiBoYXZlIHRvIGJlIHVuaXF1
ZSB3aXRoaW4gdGhlIDxyZWdpbmZvPi4NCiAgICA+IA0KICAgID4gICAgICAgIFRoZSBhY3R1YWwg
bmFtZSBvZiB0aGUgQU9SIGRpc3BsYXllZCB0byB0aGUgdXNlciBvbiB0aGUgZGV2aWNlIGlzIGxp
a2VseQ0KICAgID4gICAgICAgIHRvIGJlIGN1c3RvbWl6ZWQsIGJ1dCBJIHdhcyBwcm9iYWJseSB3
cm9uZyByZWdhcmRpbmcgdGhlIDxkaXNwbGF5LW5hbWU+DQogICAgPiAgICAgICAgZWxlbWVudCBo
ZXJlIC0tIGl0J3MgdGFrZW4gZnJvbSB0aGUgQ29udGFjdCBoZWFkZXIgaW4gdGhlIFJFR0lTVEVS
DQogICAgPiAgICAgICAgcmVxdWVzdCwgYW5kIG1vc3QgbGlrZWx5IGlzIGVtcHR5Lg0KICAgID4g
DQogICAgPiAgICAgICAgVGhlIHNpcC5pbnN0YW5jZSBpbiB0aGUgQ29udGFjdCB3aWxsIHNob3cg
dXAgYXMgYW4gPHVua25vd24tcGFyYW0+DQogICAgPiAgICAgICAgZWxlbWVudCwgYnV0IGl0IHNo
b3VsZCBiZSB0aGUgc2FtZSBmb3IgYWxsIDxjb250YWN0PiBlbGVtZW50cyBmb3INCiAgICA+ICAg
ICAgICByZWdpc3RyYXRpb25zIGZyb20gdGhlIHNhbWUgVUEuDQogICAgPiANCiAgICA+ICAgICAg
ICBUaGUgPHVyaT4gZWxlbWVudCAtLSB0aGUgY29udGFjdCBVUkkgLS0gaXMgbGlrZWx5IHRvIGNv
bnRhaW4gYm90aCBzb21lDQogICAgPiAgICAgICAgcGFydCBvZiB0aGUgQU9SIGFuZCB0aGUgSVAg
YWRkcmVzcyBvZiB0aGUgVUEsIGFuZCBzbyB0aGV5J3JlIGxpa2VseSB0bw0KICAgID4gICAgICAg
IGJlIGRpZmZlcmVudCBmb3IgZXZlcnkgPGNvbnRhY3Q+IGVsZW1lbnQuDQogICAgPiANCiAgICA+
ICAgICAgICBTbyBhbnkgc2NoZW1lIGZvciBhYnJpZGdpbmcgcmVnaXN0cmF0aW9uIGV2ZW50cyBp
cyBsaWtlbHkgdG8gaGF2ZSB0bw0KICAgID4gICAgICAgIGRlYWwgd2l0aCB1bmlxdWVzcyBpbiB0
aGUgPHVyaT4gYW5kICdpZCcgc3RyaW5ncy4NCiAgICA+IA0KICAgID4gICAgICAgIEEgYmV0dGVy
IHdheSB0byBqdWRnZSB0aGlzIGlzIHRvIGxvb2sgYXQgYSAqcmVhbCogcmVnaXN0cmF0aW9uIGV2
ZW50IGZvcg0KICAgID4gICAgICAgIGEgc2l0dWF0aW9uIGxpa2UgdGhpcyAtLSBzYXksIHRocmVl
IFVBcyByZWdpc3RlcmVkIGZvciB0aGUgc2FtZSB0aHJlZQ0KICAgID4gICAgICAgIEFPUnMuICBE
b2VzIGFueW9uZSBoYXZlIGFueSBleGFtcGxlcyB0byBzaGFyZT8NCiAgICA+IA0KICAgID4gICAg
ICAgIERhbGUNCiAgICA+IA0KICAgID4gDQogICAgPiAgICBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgID4gICAgc2lwY29yZSBtYWlsaW5nIGxpc3QN
CiAgICA+ICAgIHNpcGNvcmVAaWV0Zi5vcmcNCiAgICA+ICAgIGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vc2lwY29yZQ0KICAgID4gDQogICAgPiANCiAgICANCiAgICANCg0K


From nobody Tue Apr 16 16:32:28 2019
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B6012026E for <sipcore@ietfa.amsl.com>; Tue, 16 Apr 2019 16:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 ubmpt_L0ybcx for <sipcore@ietfa.amsl.com>; Tue, 16 Apr 2019 16:32:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 73CD4120269 for <sipcore@ietf.org>; Tue, 16 Apr 2019 16:32:23 -0700 (PDT)
Received: from [IPv6:2607:fb90:4432:4346:0:1e:3f25:aa01] ([IPv6:2607:fb90:4432:4346:0:1e:3f25:aa01]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x3GNWLnj067824 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <sipcore@ietf.org>; Tue, 16 Apr 2019 18:32:22 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1555457543; bh=dcUrB6rMzsHI57XyXIf2SVE+ueWmqGH/bhiJzZORgGY=; h=Date:Subject:In-Reply-To:From:To; b=wZydTOIO7RMB/ikWNzoTdOGpbCNF0TeGwFQkn7awBqUBfezY2RzmMGeFkdNuf8KGr u+oT2U7wSt27kWJ/h0oHBxnikLV1ZN5wGPJNoBDsyuCu5xubTQKEZ0//czE4kxuzbK BDdYHhFwGuyloMrB5z+W3iJ82t9mL/1A7rWAXHRA=
Message-Id: <201904162332.x3GNWLnj067824@nostrum.com>
SavedFromEmail: mahoney@nostrum.com
Date: Tue, 16 Apr 2019 18:32:14 -0500
In-Reply-To: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com>
Importance: normal
From: "A. Jean Mahoney" <mahoney@nostrum.com>
To: SIPCORE <sipcore@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_2275075592496920"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/kgRTMBDQ9W2qGBQfArqtzkgPPl8>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2019 23:32:26 -0000

----_com.samsung.android.email_2275075592496920
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGkgYWxsLApUaGUgZHJhZnQgcmVjZWl2ZWQgc3VwcG9ydCBvbiBsaXN0wqBhbmQgdGhlIGNoYWly
cyBkaWQgbm90IGhlYXIgYW55IG9iamVjdGlvbnMgb2ZmIGxpc3QsIHNvIHRoZSBkcmFmdCBpcyBh
ZG9wdGVkIGFzIGEgV0cgaXRlbS4gUmlmYWF0LCBwbGVhc2UgcmVuYW1lIHRoZSBkcmFmdCBhcyBk
cmFmdC1pZXRmLXNpcGNvcmUtZGlnZXN0LXNjaGVtZSBhbmQgcmVzdWJtaXQuClRoYW5rcyHCoApK
ZWFuCgoKU2VudCBmcm9tIG15IHBob25lCi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0t
LS1Gcm9tOiAiQS4gSmVhbiBNYWhvbmV5IiA8bWFob25leUBub3N0cnVtLmNvbT4gRGF0ZTogNC8x
LzE5ICAzOjQ1IFBNICAoR01ULTA2OjAwKSBUbzogU0lQQ09SRSA8c2lwY29yZUBpZXRmLm9yZz4g
U3ViamVjdDogW3NpcGNvcmVdIENhbGwgZm9yIFdHIGFkb3B0aW9uOiBkcmFmdC15dXNlZi1zaXBj
b3JlLWRpZ2VzdC1zY2hlbWUgCkhpIGFsbCwKClRoaXMgaXMgYSBjYWxsIGZvciBhZG9wdGlvbiBv
ZiBkcmFmdC15dXNlZi1zaXBjb3JlLWRpZ2VzdC1zY2hlbWUgaW4gdGhlIApTSVBDT1JFIHdvcmtp
bmcgZ3JvdXAuCgpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC15dXNlZi1z
aXBjb3JlLWRpZ2VzdC1zY2hlbWUvCgpQbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIHRvIHRoZSBs
aXN0IG9yIHRvIHRoZSBjaGFpcnMgYnkgQXByaWwgMTV0aC4KClRoYW5rcyEKCkplYW4KCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnNpcGNvcmUgbWFpbGlu
ZyBsaXN0CnNpcGNvcmVAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zaXBjb3JlCg==

----_com.samsung.android.email_2275075592496920
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2PkhpIGFsbCw8L2Rpdj48ZGl2
Pjxicj48L2Rpdj48ZGl2PlRoZSBkcmFmdCByZWNlaXZlZCBzdXBwb3J0IDxmb250IGZhY2U9InNh
bnMtc2VyaWYiPm9uIGxpc3QmbmJzcDs8L2ZvbnQ+YW5kIHRoZSBjaGFpcnMgZGlkIG5vdCBoZWFy
IGFueSBvYmplY3Rpb25zIG9mZiBsaXN0LCBzbyB0aGUgZHJhZnQgaXMgYWRvcHRlZCBhcyBhIFdH
IGl0ZW0uIFJpZmFhdCwgcGxlYXNlIHJlbmFtZSB0aGUgZHJhZnQgYXMgZHJhZnQtaWV0Zi1zaXBj
b3JlLWRpZ2VzdC1zY2hlbWUgYW5kIHJlc3VibWl0LjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+
VGhhbmtzISZuYnNwOzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+SmVhbjwvZGl2PjxkaXY+PGJy
PjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgaWQ9ImNvbXBvc2VyX3Np
Z25hdHVyZSI+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0
bWw7IGNoYXJzZXQ9VVRGLTgiPjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTo4NSU7Y29sb3I6IzU3NTc1
NyI+U2VudCBmcm9tIG15IHBob25lPC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBzdHls
ZT0iZm9udC1zaXplOjEwMCU7Y29sb3I6IzAwMDAwMCI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1z
aXplOjEwMCU7Y29sb3I6IzAwMDAwMCI+PCEtLSBvcmlnaW5hbE1lc3NhZ2UgLS0+PGRpdj4tLS0t
LS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPC9kaXY+PGRpdj5Gcm9tOiAiQS4gSmVhbiBN
YWhvbmV5IiAmbHQ7bWFob25leUBub3N0cnVtLmNvbSZndDsgPC9kaXY+PGRpdj5EYXRlOiA0LzEv
MTkgIDM6NDUgUE0gIChHTVQtMDY6MDApIDwvZGl2PjxkaXY+VG86IFNJUENPUkUgJmx0O3NpcGNv
cmVAaWV0Zi5vcmcmZ3Q7IDwvZGl2PjxkaXY+U3ViamVjdDogW3NpcGNvcmVdIENhbGwgZm9yIFdH
IGFkb3B0aW9uOiBkcmFmdC15dXNlZi1zaXBjb3JlLWRpZ2VzdC1zY2hlbWUgPC9kaXY+PGRpdj48
YnI+PC9kaXY+PC9kaXY+SGkgYWxsLDxicj48YnI+VGhpcyBpcyBhIGNhbGwgZm9yIGFkb3B0aW9u
IG9mIGRyYWZ0LXl1c2VmLXNpcGNvcmUtZGlnZXN0LXNjaGVtZSBpbiB0aGUgPGJyPlNJUENPUkUg
d29ya2luZyBncm91cC48YnI+PGJyPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LXl1c2VmLXNpcGNvcmUtZGlnZXN0LXNjaGVtZS88YnI+PGJyPlBsZWFzZSBzZW5kIHlvdXIg
Y29tbWVudHMgdG8gdGhlIGxpc3Qgb3IgdG8gdGhlIGNoYWlycyBieSBBcHJpbCAxNXRoLjxicj48
YnI+VGhhbmtzITxicj48YnI+SmVhbjxicj48YnI+X19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188YnI+c2lwY29yZSBtYWlsaW5nIGxpc3Q8YnI+c2lwY29yZUBp
ZXRmLm9yZzxicj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcGNvcmU8
YnI+PC9ib2R5PjwvaHRtbD4=

----_com.samsung.android.email_2275075592496920--


From nobody Wed Apr 17 18:41:20 2019
Return-Path: <adam@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34EE1120272 for <sipcore@ietfa.amsl.com>; Wed, 17 Apr 2019 18:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level: 
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 YMhsUAff7mRl for <sipcore@ietfa.amsl.com>; Wed, 17 Apr 2019 18:41:15 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 49B0B120270 for <sipcore@ietf.org>; Wed, 17 Apr 2019 18:41:15 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x3I1fCtE019496 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 17 Apr 2019 20:41:14 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1555551674; bh=7hs+L+0gaJKNVXAf2HKS0nNKfF8ACYCTc49YGz1cjTE=; h=To:Cc:From:Subject:Date; b=l/pgNSA2nkegqeTJPZlbKZM3CEWfhBhI0Nmmr6gBJbmbyprzHFTpZ1fhwvboAiMaU F6iNsga9cTOpDesFiL9gAojYaKAty04nMAxrVsYFRQUV3einx4DsjDx1xODtxOWAvT 5F61FPNUfh6H4EIO8WrbL4KzAUS89Qe6XP45XxBI=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: draft-ietf-sipcore-rejected.all@tools.ietf.org
Cc: "'SIPCORE'" <sipcore@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <2bed1f29-cf3e-e6df-60b8-590b88ab95d8@nostrum.com>
Date: Wed, 17 Apr 2019 20:41:07 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/86w0ExaPcD6mVyw23k03msUtHII>
Subject: [sipcore] AD Review: draft-ietf-sipcore-rejected
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 01:41:19 -0000

This is my AD review for draft-ietf-sipcore-rejected. There are a few places
where I think the mechanism needs to be better defined -- or, at least, more
clearly described -- before it goes into IETF review. I've grouped those 
issues
together at the top of my comments that follow.

---------------------------------------------------------------------------

§4.1:

This example is perplexing in a few dimensions that should be either
changed or explained. These are confusing enough that I'd like to see a new
version of the document before putting it into IETF last call.

The first is that its Call-Info header field indicates a URL of the form:

   https://block.example.net/complaint.json

...which strongly implies that one might find a JSON object at that 
location. It
then goes on to specify that the thing one would retrieve from this 
location is
a JWS. While there's nothing that technically binds a URL's name to the 
content
type found at that URL, this goes against fairly well-established 
conventions in
a way that is likely to confuse implementors.

That would imply a change to:

   https://block.example.net/complaint.jws

But this leads us to the second problem: the form of the URL -- a domain
followed by a simple word -- implies that this same URL is used for all
rejected calls (and... one would assume is generated on the fly with a fresh
"iat" parameter?)  If that's the case, then this URL becomes an oracle that
allows for the exact kind of replay attacks described in the 
introduction. To
prevent this from being such an oracle, it's going to minimally need to vary
by call, which would lead it to look more like:

https://block.example.net/79048YzkxNDA5NTI1MzA0OWFjOTFkMmFlODhiNTI2OWQ1ZTI.jws

However, this takes us to yet a third problem, which is -- even with a
JWS-per-rejected-call approach, nothing prevents an attacker from 
spoofing 608
responses with this URL for as long as the "iat" is likely to be accepted by
callers (probably on the order of minutes), which can still cause some 
pretty
substantial damage.

I *think* this requires the ability to bind the jCard-containing JWS to the
call. This would require additional claims to be added to the body. You 
could
re-use the "orig" and "dest" claims created by PASSPORT (but be wary of
retargeting), or come up with your own claims that bind the rejection to the
call (although be careful of choosing fields that may be fragile in the
presence of B2BUAs); but I think the whole signing mechanism just 
doesn't work
unless it's bound to the call in some way. It might be enough just to 
bind it to
the calling party, since that reduces the attack from a DDoS to a simple
one-device DoS.

Note that this last problem doesn't really bear on the example itself; 
however,
I wasn't completely convinced that it was an issue until I got to the 
example.

---------------------------------------------------------------------------

§4.4, Figure 5:

This is an issue that I'd like to see fixed before IETF last call.

Please either show the use of PRACK with the 183 response, or indicate 
that the
required PRACK messages have been elided from the diagram for clarity. 
In either
case, this document must have RFC 3262 as a normative dependency, as it's
impossible to satisfy its normatively-required behaviors without that
mechanism.

---------------------------------------------------------------------------

§6:

This is an issue that I'd like to see fixed before IETF last call.

The mechanism specifies that the JWS objects are required to contain an 
"iat"
claim, but provides no guidance for how the recipient of such a JWS is 
supposed
to use this information. Clearly, it's intended to be "fresh enough" to 
prevent
replay attacks, but this is never stated.

You should be able to fix this (once the first issue above is addressed) by
adding something to the "Security Considerations" section modeled after
https://tools.ietf.org/html/rfc8225#section-10.1

===========================================================================

My remaining comments are non-blocking, and can be handled at the same 
time as
other IETF last call comments.

---------------------------------------------------------------------------

Please expand the following acronyms upon first use and in the title;
see https://www.rfc-editor.org/materials/abbrev.expansion.txt for guidance.

  - UAS - User Agent Server
  - JOSE - JSON Object Signing and Encryption
  - JWT - JSON Web Token
  - JWS - JSON Web Signature
  - UAC - User Agent Client
  - JWA - JSON Web Algorithms
  - SDP - Session Description Protocol

---------------------------------------------------------------------------

Abstract:

 >  The present use case driving the need
 >  for the 608 response code is when the intermediary is an analytics
 >  engine.

The use of "present" won't age well. Suggest changing to "initial."

---------------------------------------------------------------------------

§1:

 >  was unwanted.  As RFC8197 explains, not only does the called party

Nit: "[RFC8197]" or "RFC 8197"

 >  call analytics engine.  For various reasons described in RFC8197, if

Same as above.

 >  does not want the call.  However, RFC8197 specifies that one of the

Same as above.

---------------------------------------------------------------------------

§1:

 >  An algorithm can be vulnerable to the base rate
 >  fallacy base rate fallacy [BaseRate] algorithm rejecting the call.

This sentence is difficult to follow. Please re-write for clarity.

---------------------------------------------------------------------------

§1:

 >  One might ask why we cannot use the same mechanism an analytics
 >  service provider offers their customers that lets them correct a call
 >  blocked in error?

Nit: replace "?" with "."

---------------------------------------------------------------------------

1:

 >  The protocol described in this document uses existing IETF protocol
 >  mechanisms...

This reads a bit awkwardly. Consider "...existing SIP protocol 
mechanisms..."

---------------------------------------------------------------------------

§1:

 >  ...we have a standard marshaling mechanism for
 >  creating a canonical representation of a JSON [RFC8259] object...

I don't think this is true as stated, nor is it needed for this 
document. There
are ongoing discussions about defining a standardized canonical 
serialization of
JSON objects, but those discussions are still in their very earliest stages.

---------------------------------------------------------------------------

§1:

 >  Suppose, for
 >  example, that the redress address was simply passed as a header
 >  value.

Nit: "...header field value."

---------------------------------------------------------------------------

§1:

 >  The jCard encoding might seem unnecessary at first, but it is...

This paragraph is confusing, as there's nothing inherent in jCard that 
does any
of the things this paragraph claims. I think changing "jCard" to "Signed 
jCard"
probably fixes this.

---------------------------------------------------------------------------

§3.1:

 >  In this situation, the requirements stated in Section 16.7 of RFC3261
 >  [RFC3261] apply.

Nit: remove the initial "RFC3261".

---------------------------------------------------------------------------

§3.2:

 > 3.2.  jCard Construction
 >
 >    The intermediary constructs the JWS as follows.

This is a bit confusing: the section header indicates that this talks about
jCard construction, while the prose indicates that it talks about JWS
construction. I suggest adjusting the title.

---------------------------------------------------------------------------

§3.4:

 >  they will pass headers such as "Feature-Caps: *;+sip.608" unmodified.

Nit: "...pass header fields such as..."

---------------------------------------------------------------------------

§4.1:

 >  Contact: <sip:+12155550112@2001:db8::12:50207;rinstance=9da3088f36cc>

Thanks for using IPv6 in your examples! Please reformat according to the 
rules
for IPv6 addresses in URIs (note the brackets):

    Contact: <sip:+12155550112@[2001:db8::12]:50207;rinstance=9da3088f36cc>

 >  Via: SIP/2.0/UDP 2001:db8::177:60012;branch=z9hG4bK-524287-1

Similarly:

    Via: SIP/2.0/UDP [2001:db8::177]:60012;branch=z9hG4bK-524287-1

---------------------------------------------------------------------------

§4.1:

All of the JWS examples in this document use vanilla Base64 encoding, rather
than the "Base64url" encoding defined in section 2 of RFC 7515. None of them
are syntactically valid JWS. Please see RFC 7515 Appendix C for guidance.

---------------------------------------------------------------------------

§4.4:

 >  608.  Per RFC6809 [RFC6809], the SBC can insert "*;+sip.608" into the

Please remove the redundant "RFC6809".

---------------------------------------------------------------------------

§4.4, Figure 5:

It's a bit unconventional for a ladder diagram to have the initiating action
start from the right-hand-side of the diagram. Consider reversing the 
order of
elements left-to-right.

---------------------------------------------------------------------------

§6:

 >  Intermediary operators need to be mindful of whom they are sending
 >  the 608 response.

This is missing a preposition. I suggest adding a "to" either before 
"whom" or
after "response" (depending on how formally correct you wish to be).

---------------------------------------------------------------------------

§6:

    more significant risk, is that by providing a contact in the Call-
    Info field, the intermediary may be giving the malicious caller a

Nit: "...header field..."

---------------------------------------------------------------------------

§6:

 >  Because
 >  the mechanism described here can result in an audio file being sent
 >  to the target of the Contact header field,

This isn't right. The target of the attack would need to be indicated in 
the SDP
of the INVITE, not the Contact header field. Basically, this describes 
the exact
same attack that RFC 5245 section 18.5.1 does. I don't mention this for the
purpose of citing RFC 5245 (which has been superseded by RFC 8445, which 
lacks a
corresponding section), but to point out that the security considerations
section in this document should at least mention ICE as a mitigation 
technique
for this attack.


From nobody Thu Apr 18 09:01:54 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBF612032B; Thu, 18 Apr 2019 09:01:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <155560331211.29947.17873484433101041536@ietfa.amsl.com>
Date: Thu, 18 Apr 2019 09:01:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ZlL0toh2vaptR6dglKOwXbdvmdg>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-00.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 16:01:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Protocol Core WG of the IETF.

        Title           : The Session Initiation Protocol (SIP) Digest Authentication Scheme
        Author          : Rifaat Shekh-Yusef
	Filename        : draft-ietf-sipcore-digest-scheme-00.txt
	Pages           : 8
	Date            : 2019-04-18

Abstract:
   This document updates the Digest Access Authentication scheme used by
   the Session Initiation Protocol (SIP) to add support for secure
   digest algorithms to replace the broken MD5 algorithm.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-digest-scheme/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-sipcore-digest-scheme-00
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-digest-scheme-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Apr 18 09:06:27 2019
Return-Path: <rifaat.ietf@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBBC12032B; Thu, 18 Apr 2019 09:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HCithdAU6gnD; Thu, 18 Apr 2019 09:06:24 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 031D3120157; Thu, 18 Apr 2019 09:06:24 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id p23so2285969iol.13; Thu, 18 Apr 2019 09:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3/j65gg5nio7szFaQ/Xj8AHj0UkqR1W9QExfRPQ/wUs=; b=l6Vdl6p6yJp2MLWtm/CfPzbU86DFS67uh8c5yYnOxS9KwQjKmiD9+yh0xWpS0gE04e oIznDBUMYjQSVeOVKCFe9EvKZrsLNWU9D+lrTb6xoXIUcR/flAkXkzPTn5/J6rso7FjL cTdybA2VJvxCeYTEncw6UejVkzNt+Sk+db+NvV3ZWT1SfBwq0Y0Z9+xXjoHQHHHfxl5U Qx0adRqtjbGpWdWU6ExtMfiYii3v4qP3DE6kbrGkyKQfMbY8kcZRC2G76LeyMhxPmtCB t7fuGeP/D1MyvxC4xdOdeGkmc8sdZzfZlpTGzl9VHKSWxi+MSV1aV4kgxYJykcPg0Qur glWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3/j65gg5nio7szFaQ/Xj8AHj0UkqR1W9QExfRPQ/wUs=; b=e31N8klCxE2U/CZkdyevOOp0kcSoHkg3dtgZS1c7ZUr2ZR+A1Y1rtU8oXBdVdx7OgR elJmUpWWvccmv5nep2QXqkoSMxNzj7dsWcIuih764cuHhi8rOeV1UiwA8nYSHu/fuU0a Wpp36OiXiII1wHkaSfwdg94gQUERWsJpusXSOJbFd629KJHypWPTLXxidxl1WhtCrUjx eLLcBDoCKyFRRxittIYPf9MUKWJgalP+KMjFQAtU8e9aJ8CAy5gpnXRSx2F2dJ456vBS mHSyybMsFHs6d8DdY1k8IVc1Vbz/Tpvb3zrRyPkTgYIsfnkpHudGI8ETChwZldVNCtXf omoQ==
X-Gm-Message-State: APjAAAWlHgBIRtdOIaKielxhL75f1S2BEN4V3TarzRF6dDB6ywQYjHYJ 5zltGSQyyQavw2xJ3JWPYvoa8a5u1U+Wfffqm/sPeGet5us=
X-Google-Smtp-Source: APXvYqyp5+Qm/asliCycD0+bX2tksg6QUf2x/su+1cwlPSdMSHdosvofVUOUO0EyuFsPkY59r3Jh7qunOP34LO9rpIw=
X-Received: by 2002:a5d:8597:: with SMTP id f23mr1881025ioj.148.1555603582978;  Thu, 18 Apr 2019 09:06:22 -0700 (PDT)
MIME-Version: 1.0
References: <155560331211.29947.17873484433101041536@ietfa.amsl.com>
In-Reply-To: <155560331211.29947.17873484433101041536@ietfa.amsl.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Thu, 18 Apr 2019 12:06:11 -0400
Message-ID: <CAGL6epLNrSFkpdM7jLrW0Q8y+Wzq9dQO1Bt+ycCmDDNZjtbo0A@mail.gmail.com>
To: SIPCORE <sipcore@ietf.org>
Cc: i-d-announce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f991bc0586d02ec5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/-wLu1BQL2h3QolyKpqz-wwNe3N0>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-00.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 16:06:26 -0000

--000000000000f991bc0586d02ec5
Content-Type: text/plain; charset="UTF-8"

All,

I have updated the document based on the recent feedback, and I believe
that this document is ready for WGLC.
Anybody thinks otherwise?

Regards,
 Rifaat


On Thu, Apr 18, 2019 at 12:02 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session Initiation Protocol Core WG of
> the IETF.
>
>         Title           : The Session Initiation Protocol (SIP) Digest
> Authentication Scheme
>         Author          : Rifaat Shekh-Yusef
>         Filename        : draft-ietf-sipcore-digest-scheme-00.txt
>         Pages           : 8
>         Date            : 2019-04-18
>
> Abstract:
>    This document updates the Digest Access Authentication scheme used by
>    the Session Initiation Protocol (SIP) to add support for secure
>    digest algorithms to replace the broken MD5 algorithm.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-digest-scheme/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sipcore-digest-scheme-00
> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-digest-scheme-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

--000000000000f991bc0586d02ec5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">All,<div><br></div><div>I have updated the document based =
on the recent feedback, and I believe that this document is ready for WGLC.=
</div><div>Anybody thinks otherwise?<br></div><div><br></div><div>Regards,<=
/div><div>=C2=A0Rifaat</div><div><br></div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr 18, 2019 at 12:02 PM=
 &lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><b=
r>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Session Initiation Protocol Core WG of the=
 IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 The Session Initiation Protocol (SIP) Digest Authentication Scheme<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Rifa=
at Shekh-Yusef<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-sipcore-digest-scheme-00.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 8<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-04-18<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document updates the Digest Access Authentication scheme =
used by<br>
=C2=A0 =C2=A0the Session Initiation Protocol (SIP) to add support for secur=
e<br>
=C2=A0 =C2=A0digest algorithms to replace the broken MD5 algorithm.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-sipcore-digest-schem=
e/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-sipcore-digest-scheme/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-sipcore-digest-scheme-00"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-iet=
f-sipcore-digest-scheme-00</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-digest-=
scheme-00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/html/draft-ietf-sipcore-digest-scheme-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sipcore" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore</a><br>
</blockquote></div>

--000000000000f991bc0586d02ec5--


From nobody Mon Apr 22 01:18:25 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5A8D120059 for <sipcore@ietfa.amsl.com>; Mon, 22 Apr 2019 01:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 Eit4Ud0b2CDS for <sipcore@ietfa.amsl.com>; Mon, 22 Apr 2019 01:18:22 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-ve1eur02on0630.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe06::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96FE71200DB for <sipcore@ietf.org>; Mon, 22 Apr 2019 01:18:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qksT3+My48Q23WytGuB3rwlkJw263HEq2zaE3wIzxCM=; b=KGyM8oPeWlHxi+zGwmKUdVamqTuEMcsM4fVb8NAXBLl7rr9IicGkGF66UTAZxhLsMq2iM6CVnNiZ63tel0UQO1Tak03eqTrnNeNhEEscm8t3BAY2q1567HT+9QQDGGVuWwL71WPSWqJ0oOvQV9ulttjadcA+uOl80xRO7jhKwRo=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3515.eurprd07.prod.outlook.com (10.170.248.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1835.11; Mon, 22 Apr 2019 08:18:18 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::747a:900a:3053:2184]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::747a:900a:3053:2184%2]) with mapi id 15.20.1835.010; Mon, 22 Apr 2019 08:18:18 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, SIPCORE <sipcore@ietf.org>
Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-00.txt
Thread-Index: AQHU9gAfRvw7V7xJaU+yjK9seo8YtaZCFUeAgAX444A=
Date: Mon, 22 Apr 2019 08:18:18 +0000
Message-ID: <266C1627-8DE0-4484-9684-A022155C879F@ericsson.com>
References: <155560331211.29947.17873484433101041536@ietfa.amsl.com> <CAGL6epLNrSFkpdM7jLrW0Q8y+Wzq9dQO1Bt+ycCmDDNZjtbo0A@mail.gmail.com>
In-Reply-To: <CAGL6epLNrSFkpdM7jLrW0Q8y+Wzq9dQO1Bt+ycCmDDNZjtbo0A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [176.93.29.18]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ab6d48f4-097e-4cc2-dd0b-08d6c6fb137f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR07MB3515; 
x-ms-traffictypediagnostic: HE1PR07MB3515:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <HE1PR07MB3515E280C36EBD660A43F03E93220@HE1PR07MB3515.eurprd07.prod.outlook.com>
x-forefront-prvs: 00159D1518
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(376002)(39860400002)(366004)(346002)(189003)(199004)(18543002)(2906002)(25786009)(6512007)(6436002)(110136005)(58126008)(14444005)(66574012)(256004)(83716004)(316002)(53936002)(3846002)(6116002)(99286004)(6246003)(6306002)(54896002)(606006)(53386004)(71200400001)(5660300002)(82746002)(71190400001)(76176011)(229853002)(236005)(6486002)(66066001)(14454004)(66946007)(36756003)(966005)(476003)(2616005)(76116006)(446003)(11346002)(486006)(44832011)(86362001)(66556008)(33656002)(64756008)(66476007)(66446008)(73956011)(68736007)(6506007)(102836004)(53546011)(81156014)(8936002)(26005)(7736002)(186003)(478600001)(8676002)(81166006)(97736004)(554374003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3515; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: YRyNYA76KpNbULwDiQ9uibrzI8CBpYAaGmm0KvPgIQ4CjM6qwRKw/Skp1vCMsvVI9Bn42YgSBS+0c8sPNWyw29CqDZMikiKlYSsclXIJukWVx+Q0jEcJ31mY9K09GgXeESHILUnYe4mDRwhhi//xBu84EIHe4HNfrc+TxTnRtqXjEsdGta4nb00Y3nMkmMdIvm5txb3AJqVmP/tY8kNKCH0DS1bmWpS6XcaOTGaDJJUc6X2P94s4dHkKnrMU9jigHZTf9dqkeYUdR9RCIiKbDyGgvJcrxT0Jj1DUu3uKZo9iT40lgwotAxPb3kqVg4I4J1RHzuE8atzyiK+uiWWOjZH4VDykYJPbA2wN0bms9dSP13hVtCW87dPBISBbks2RXgiOMVMTljWo1DwX2UsRYgspscwTqUMi41ILWBDypQE=
Content-Type: multipart/alternative; boundary="_000_266C16278DE044849684A022155C879Fericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ab6d48f4-097e-4cc2-dd0b-08d6c6fb137f
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2019 08:18:18.4790 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3515
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/JEvJAgZtDK4jq-FhOxQH8JBZK-s>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-00.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2019 08:18:24 -0000

--_000_266C16278DE044849684A022155C879Fericssoncom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCkkgdGhpbmsgd2UgYXJlIG1vcmUgb3IgbGVzcyByZWFkeSBmb3IgV0dMQy4gSSBhbSBz
dGlsbCB3YWl0aW5nIGZvciBjb21tZW50cyBmcm9tIHNvbWUgcGVvcGxlIEkgaGF2ZSBmb3J3YXJk
ZWQgdGhlIGRyYWZ0IHRvLCBidXQgd2UgZG9u4oCZdCBuZWVkIHRvIGhvbGQgdGhlIFdHTEMgYmVj
YXVzZSBvZiB0aGF0Lg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpGcm9tOiBzaXBjb3JlIDxz
aXBjb3JlLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBSaWZhYXQgU2hla2gtWXVzZWYg
PHJpZmFhdC5pZXRmQGdtYWlsLmNvbT4NCkRhdGU6IFRodXJzZGF5LCAxOCBBcHJpbCAyMDE5IGF0
IDE5LjA2DQpUbzogInNpcGNvcmVAaWV0Zi5vcmciIDxzaXBjb3JlQGlldGYub3JnPg0KQ2M6ICJp
LWQtYW5ub3VuY2VAaWV0Zi5vcmciIDxpLWQtYW5ub3VuY2VAaWV0Zi5vcmc+DQpTdWJqZWN0OiBS
ZTogW3NpcGNvcmVdIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtc2lwY29yZS1kaWdlc3Qtc2NoZW1l
LTAwLnR4dA0KDQpBbGwsDQoNCkkgaGF2ZSB1cGRhdGVkIHRoZSBkb2N1bWVudCBiYXNlZCBvbiB0
aGUgcmVjZW50IGZlZWRiYWNrLCBhbmQgSSBiZWxpZXZlIHRoYXQgdGhpcyBkb2N1bWVudCBpcyBy
ZWFkeSBmb3IgV0dMQy4NCkFueWJvZHkgdGhpbmtzIG90aGVyd2lzZT8NCg0KUmVnYXJkcywNCiBS
aWZhYXQNCg0KDQpPbiBUaHUsIEFwciAxOCwgMjAxOSBhdCAxMjowMiBQTSA8aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnPG1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+PiB3cm90ZToNCg0K
QSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJu
ZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUg
U2Vzc2lvbiBJbml0aWF0aW9uIFByb3RvY29sIENvcmUgV0cgb2YgdGhlIElFVEYuDQoNCiAgICAg
ICAgVGl0bGUgICAgICAgICAgIDogVGhlIFNlc3Npb24gSW5pdGlhdGlvbiBQcm90b2NvbCAoU0lQ
KSBEaWdlc3QgQXV0aGVudGljYXRpb24gU2NoZW1lDQogICAgICAgIEF1dGhvciAgICAgICAgICA6
IFJpZmFhdCBTaGVraC1ZdXNlZg0KICAgICAgICBGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1pZXRm
LXNpcGNvcmUtZGlnZXN0LXNjaGVtZS0wMC50eHQNCiAgICAgICAgUGFnZXMgICAgICAgICAgIDog
OA0KICAgICAgICBEYXRlICAgICAgICAgICAgOiAyMDE5LTA0LTE4DQoNCkFic3RyYWN0Og0KICAg
VGhpcyBkb2N1bWVudCB1cGRhdGVzIHRoZSBEaWdlc3QgQWNjZXNzIEF1dGhlbnRpY2F0aW9uIHNj
aGVtZSB1c2VkIGJ5DQogICB0aGUgU2Vzc2lvbiBJbml0aWF0aW9uIFByb3RvY29sIChTSVApIHRv
IGFkZCBzdXBwb3J0IGZvciBzZWN1cmUNCiAgIGRpZ2VzdCBhbGdvcml0aG1zIHRvIHJlcGxhY2Ug
dGhlIGJyb2tlbiBNRDUgYWxnb3JpdGhtLg0KDQoNClRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1
cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi1zaXBjb3JlLWRpZ2VzdC1zY2hlbWUvDQoNClRoZXJlIGFyZSBhbHNvIGh0
bWxpemVkIHZlcnNpb25zIGF2YWlsYWJsZSBhdDoNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1pZXRmLXNpcGNvcmUtZGlnZXN0LXNjaGVtZS0wMA0KaHR0cHM6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1pZXRmLXNpcGNvcmUtZGlnZXN0LXNjaGVtZS0wMA0K
DQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9t
IHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBk
aWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmc8aHR0cDovL3Rvb2xzLmlldGYub3Jn
Pi4NCg0KSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQ
IGF0Og0KZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnNpcGNvcmUgbWFpbGluZyBsaXN0
DQpzaXBjb3JlQGlldGYub3JnPG1haWx0bzpzaXBjb3JlQGlldGYub3JnPg0KaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXBjb3JlDQo=

--_000_266C16278DE044849684A022155C879Fericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <40D9F485AE8D5B4BB26435AAE95FD5D8@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzAu
ODVwdCAyLjBjbSA3MC44NXB0IDIuMGNtO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk
U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkZJIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5IaSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPkkgdGhpbmsgd2UgYXJlIG1vcmUgb3IgbGVzcyByZWFkeSBmb3IgV0dMQy4gSSBhbSBzdGls
bCB3YWl0aW5nIGZvciBjb21tZW50cyBmcm9tIHNvbWUgcGVvcGxlIEkgaGF2ZSBmb3J3YXJkZWQg
dGhlIGRyYWZ0IHRvLCBidXQgd2UgZG9u4oCZdCBuZWVkIHRvIGhvbGQgdGhlIFdHTEMgYmVjYXVz
ZSBvZiB0aGF0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PkNocmlzdGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0
IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5Gcm9tOiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5zaXBjb3JlICZsdDtzaXBjb3JlLWJvdW5jZXNA
aWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiBSaWZhYXQgU2hla2gtWXVzZWYgJmx0O3JpZmFhdC5p
ZXRmQGdtYWlsLmNvbSZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+VGh1cnNkYXksIDE4IEFwcmlsIDIw
MTkgYXQgMTkuMDY8YnI+DQo8Yj5UbzogPC9iPiZxdW90O3NpcGNvcmVAaWV0Zi5vcmcmcXVvdDsg
Jmx0O3NpcGNvcmVAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVvdDtpLWQtYW5ub3Vu
Y2VAaWV0Zi5vcmcmcXVvdDsgJmx0O2ktZC1hbm5vdW5jZUBpZXRmLm9yZyZndDs8YnI+DQo8Yj5T
dWJqZWN0OiA8L2I+UmU6IFtzaXBjb3JlXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLXNpcGNvcmUt
ZGlnZXN0LXNjaGVtZS0wMC50eHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFsbCwgPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGhhdmUgdXBkYXRlZCB0aGUgZG9jdW1lbnQgYmFzZWQgb24g
dGhlIHJlY2VudCBmZWVkYmFjaywgYW5kIEkgYmVsaWV2ZSB0aGF0IHRoaXMgZG9jdW1lbnQgaXMg
cmVhZHkgZm9yIFdHTEMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5Bbnlib2R5IHRoaW5rcyBvdGhlcndpc2U/PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlJlZ2FyZHMsPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDtSaWZhYXQ8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUaHUs
IEFwciAxOCwgMjAxOSBhdCAxMjowMiBQTSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmludGVybmV0LWRy
YWZ0c0BpZXRmLm9yZyI+aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPC9hPiZndDsgd3JvdGU6PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFy
Z2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
YnI+DQpBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJ
bnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuPGJyPg0KVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRl
bSBvZiB0aGUgU2Vzc2lvbiBJbml0aWF0aW9uIFByb3RvY29sIENvcmUgV0cgb2YgdGhlIElFVEYu
PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFRpdGxlJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDs6IFRoZSBTZXNzaW9uIEluaXRpYXRpb24gUHJv
dG9jb2wgKFNJUCkgRGlnZXN0IEF1dGhlbnRpY2F0aW9uIFNjaGVtZTxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBBdXRob3ImbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IDogUmlmYWF0IFNoZWtoLVl1c2VmPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEZp
bGVuYW1lJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDogZHJhZnQtaWV0Zi1zaXBjb3JlLWRp
Z2VzdC1zY2hlbWUtMDAudHh0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFBhZ2Vz
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDs6IDg8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgRGF0ZSZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7IDogMjAxOS0wNC0xODxicj4NCjxicj4NCkFic3RyYWN0Ojxicj4NCiZuYnNwOyAm
bmJzcDtUaGlzIGRvY3VtZW50IHVwZGF0ZXMgdGhlIERpZ2VzdCBBY2Nlc3MgQXV0aGVudGljYXRp
b24gc2NoZW1lIHVzZWQgYnk8YnI+DQombmJzcDsgJm5ic3A7dGhlIFNlc3Npb24gSW5pdGlhdGlv
biBQcm90b2NvbCAoU0lQKSB0byBhZGQgc3VwcG9ydCBmb3Igc2VjdXJlPGJyPg0KJm5ic3A7ICZu
YnNwO2RpZ2VzdCBhbGdvcml0aG1zIHRvIHJlcGxhY2UgdGhlIGJyb2tlbiBNRDUgYWxnb3JpdGht
Ljxicj4NCjxicj4NCjxicj4NClRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0
aGlzIGRyYWZ0IGlzOjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWlldGYtc2lwY29yZS1kaWdlc3Qtc2NoZW1lLyIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtc2lwY29yZS1kaWdlc3Qt
c2NoZW1lLzwvYT48YnI+DQo8YnI+DQpUaGVyZSBhcmUgYWxzbyBodG1saXplZCB2ZXJzaW9ucyBh
dmFpbGFibGUgYXQ6PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWlldGYtc2lwY29yZS1kaWdlc3Qtc2NoZW1lLTAwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtc2lwY29yZS1kaWdlc3Qtc2NoZW1lLTAw
PC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwv
ZHJhZnQtaWV0Zi1zaXBjb3JlLWRpZ2VzdC1zY2hlbWUtMDAiIHRhcmdldD0iX2JsYW5rIj5odHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWlldGYtc2lwY29yZS1kaWdl
c3Qtc2NoZW1lLTAwPC9hPjxicj4NCjxicj4NCjxicj4NClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5
IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb248YnI+
DQp1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IDxh
IGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPg0KdG9vbHMuaWV0
Zi5vcmc8L2E+Ljxicj4NCjxicj4NCkludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUg
YnkgYW5vbnltb3VzIEZUUCBhdDo8YnI+DQo8YSBocmVmPSJmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzLyIgdGFyZ2V0PSJfYmxhbmsiPmZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvPC9hPjxicj4NCjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fPGJyPg0Kc2lwY29yZSBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJt
YWlsdG86c2lwY29yZUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnNpcGNvcmVAaWV0Zi5vcmc8
L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9z
aXBjb3JlIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zaXBjb3JlPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_266C16278DE044849684A022155C879Fericssoncom_--


From nobody Mon Apr 22 12:26:02 2019
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7B4F12014E for <sipcore@ietfa.amsl.com>; Mon, 22 Apr 2019 12:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 QtpPzQFPV7-g for <sipcore@ietfa.amsl.com>; Mon, 22 Apr 2019 12:25:59 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 1E253120123 for <sipcore@ietf.org>; Mon, 22 Apr 2019 12:25:58 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x3MJPvE3015080 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <sipcore@ietf.org>; Mon, 22 Apr 2019 14:25:58 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1555961158; bh=x8J2HDZZd8sZuR3Pk4+emFehNPz/idaUcCeplKCviVs=; h=To:From:Subject:Date; b=UMEWWXitiboAfpgdtM+QT1ZwDMZOhsEOl+huD1gNVAzF53maVXubXAvwpmaR4GpDg e+k8fGZf/ueFc6FzQLukhCR2SrUCtCthFwPXksE+yylrvKWs6KqTvJ9fiUFB9X1oDE usB0xDLi+3esljutKJBaO2SwWK3B+Gif5wFNySIQ=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be mutabilis-2.local
To: SIPCORE <sipcore@ietf.org>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <f3afe0a4-4e11-abdd-681f-cf276a71122c@nostrum.com>
Date: Mon, 22 Apr 2019 14:25:58 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/FvkXChELkXh4C_AQSoLptupEhYc>
Subject: [sipcore] WGLC: draft-ietf-sipcore-digest-scheme
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2019 19:26:02 -0000

Hi all,

This starts a 2-week Working Group Last Call for 
draft-ietf-sipcore-digest-scheme. Please send your comments to the list 
by May 6.

https://datatracker.ietf.org/doc/draft-ietf-sipcore-digest-scheme/

Thanks!

Jean


From nobody Mon Apr 22 23:11:50 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B0B120091 for <sipcore@ietfa.amsl.com>; Mon, 22 Apr 2019 23:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 bPBpa2dPlAOQ for <sipcore@ietfa.amsl.com>; Mon, 22 Apr 2019 23:11:46 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130047.outbound.protection.outlook.com [40.107.13.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B66A12004D for <sipcore@ietf.org>; Mon, 22 Apr 2019 23:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yXwfU+zZQnQIbkzsrfAZzOWgA03RW+FiH+dTDGVQaJA=; b=cmgrAax4NZG8K9g+mF0F2ytIVzI8EBU/do9kGTF4QwTqXonsVJbv1sXhjuyG7lWc1DAeUtQqG+37eI+XM3ThlAcal72e4+siv/wR4d48l/4hkbViol5ZdmgFUfGMip/+2OjvbttZBTxdTVQHPn7fnTAzz64Xb27l1uZClQCr91c=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB4378.eurprd07.prod.outlook.com (20.176.167.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1835.7; Tue, 23 Apr 2019 06:11:43 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::747a:900a:3053:2184]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::747a:900a:3053:2184%2]) with mapi id 15.20.1835.010; Tue, 23 Apr 2019 06:11:43 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "A. Jean Mahoney" <mahoney@nostrum.com>, SIPCORE <sipcore@ietf.org>
Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-digest-scheme - some comments from Christer
Thread-Index: AQHU+ZtsZ094fSqEHke8nZOFPGymog==
Date: Tue, 23 Apr 2019 06:11:43 +0000
Message-ID: <76792324-9AA2-45BA-9236-CCFC7770456F@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [176.72.255.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 072c479d-5dd5-4f64-9db6-08d6c7b28efa
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR07MB4378; 
x-ms-traffictypediagnostic: HE1PR07MB4378:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <HE1PR07MB4378103148659645F06F6C5D93230@HE1PR07MB4378.eurprd07.prod.outlook.com>
x-forefront-prvs: 0016DEFF96
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(346002)(136003)(366004)(396003)(18543002)(199004)(189003)(53754006)(53936002)(8676002)(14454004)(6436002)(102836004)(305945005)(36756003)(478600001)(33656002)(7736002)(68736007)(97736004)(186003)(6246003)(6306002)(966005)(6512007)(81166006)(81156014)(26005)(6486002)(6506007)(229853002)(14444005)(256004)(4744005)(86362001)(5660300002)(73956011)(76116006)(66946007)(71190400001)(8936002)(66446008)(2906002)(83716004)(476003)(66066001)(486006)(2616005)(99286004)(25786009)(58126008)(82746002)(110136005)(3846002)(66556008)(316002)(6116002)(66476007)(71200400001)(44832011)(64756008); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4378; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: hhvlAqWdgTLssSBw5lutoy5g+IxHEnfduuCdgCOkjO0cl5jZSNagY5a9rS0hvbPZOIzA54F7CkTOaaKw9IBucUC+ZSyVefgkXfc1TgCSi2DIOMJNIFphSZrasfqvcjmMykG3osUlzF8Z7jxAV7MB3V5H2wA066XFUhWUfrG+0pf3rgZHDIsEA1+K77V39ufXLeDWAQhkl9B0cTD/rfBJ1WSf/SxOUIPKapASYY6+Y8hAFAK614W6DZc6lHPV/WfuVO8yqDNeuUS1xa0ClhTsAwI5/rpdnJ5QL7UpWxgk/ndjKdSmyhrbfUQxrUYTNTeZ2Ho2rVpwJNv3vnJaQ5R5o+u4N4LYAI6bSP60MSlQCn/h0k/hFJUZEt4iArVUYM+LlS2bYxNzomqWfIQN5GvsgqrwWVwPKZr74FK1c/NSwEw=
Content-Type: text/plain; charset="utf-8"
Content-ID: <2569F3C640931146AD4A789D3412B546@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 072c479d-5dd5-4f64-9db6-08d6c7b28efa
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Apr 2019 06:11:43.5258 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4378
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/mit3ilJxRw-R4jmE4UyowpUKgLI>
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-digest-scheme - some comments from Christer
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2019 06:11:49 -0000

SGksDQoNCkJlbG93IGFyZSBhIGNvdXBsZSBvZiBlZGl0b3JpYWwgY29tbWVudHMgZnJvbSBtZToN
Cg0KLS0tDQoNClExOg0KDQpUaGUgSW50cm9kdWN0aW9uIGluZGljYXRlcyB0aGF0IDMyNjEgaXMg
dXBkYXRlZCBieSBhbGxvd2luZyBuZXcgYWxnb3JpdGhtcy4gVGhlbiBTZWN0aW9uIDIgY29udGFp
bnMgcHJvY2VkdXJlcywgYnV0IGl0IGlzIHVuY2xlYXIgd2hldGhlciB0aG9zZSBhcmUgdGhlIHNh
bWUgYXMgaW4gMzI2MSwgb3IgaWYgdGhleSB1cGRhdGUgMzI2MS4NCg0KSSB0aGluayB0aGVyZSBz
aG91bGQgYmUgYSBoZWFkIHNlY3Rpb24sICJVcGRhdGVzIHRvIFJGQyAzMjYxIiwgdGhhdCBpbmNs
dWRlcyBhbnkgdXBkYXRlZCBwcm9jZWR1cmVzLCBhbmQgdGhlIHVwZGF0ZWQgQUJORi4NCg0KLS0t
DQoNClEyOg0KDQpQbGVhc2UgdXNlICJoZWFkZXIgZmllbGQiIHRlcm1pbm9sb2d5IGluc3RlYWQg
b2YgImhlYWRlciIuDQoNCi0tLQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg0KDQrvu79P
biAyMi8wNC8yMDE5LCAyMi4yNiwgInNpcGNvcmUgb24gYmVoYWxmIG9mIEEuIEplYW4gTWFob25l
eSIgPHNpcGNvcmUtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgbWFob25leUBub3N0cnVt
LmNvbT4gd3JvdGU6DQoNCiAgICBIaSBhbGwsDQogICAgDQogICAgVGhpcyBzdGFydHMgYSAyLXdl
ZWsgV29ya2luZyBHcm91cCBMYXN0IENhbGwgZm9yIA0KICAgIGRyYWZ0LWlldGYtc2lwY29yZS1k
aWdlc3Qtc2NoZW1lLiBQbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIHRvIHRoZSBsaXN0IA0KICAg
IGJ5IE1heSA2Lg0KICAgIA0KICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtc2lwY29yZS1kaWdlc3Qtc2NoZW1lLw0KICAgIA0KICAgIFRoYW5rcyENCiAgICAN
CiAgICBKZWFuDQogICAgDQogICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCiAgICBzaXBjb3JlIG1haWxpbmcgbGlzdA0KICAgIHNpcGNvcmVAaWV0Zi5v
cmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcGNvcmUNCiAg
ICANCg0K


From nobody Tue Apr 23 19:46:25 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DFEE1202D7; Tue, 23 Apr 2019 19:46:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <155607397517.32461.8003402784805398777@ietfa.amsl.com>
Date: Tue, 23 Apr 2019 19:46:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/8YqoT71oxuxwYM19h4OpxbkQaiI>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-rejected-07.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 02:46:15 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Protocol Core WG of the IETF.

        Title           : A Session Initiation Protocol (SIP) Response Code for Rejected Calls
        Authors         : Eric W. Burger
                          Bhavik Nagda
	Filename        : draft-ietf-sipcore-rejected-07.txt
	Pages           : 24
	Date            : 2019-04-23

Abstract:
   This document defines the 608 (Rejected) SIP response code.  This
   response code enables calling parties to learn that an intermediary
   rejected their call attempt.  No one will deliver, and thus no one
   will answer, the call.  As a 6xx code, the caller will be aware that
   future attempts to contact the same User Agent Server will likely
   fail.  The initial use case driving the need for the 608 response
   code is when the intermediary is an analytics engine.  In this case,
   the rejection is by a machine or other process.  This contrasts with
   the 607 (Unwanted) SIP response code, which a human at the target
   User Agent Server indicated the user did not want the call.  In some
   jurisdictions this distinction is important.  This document also
   defines the use of the Call-Info header field in 608 responses to
   enable rejected callers to contact entities that blocked their calls
   in error.  This provides a remediation mechanism for legal callers
   that find their calls blocked.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-rejected/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-sipcore-rejected-07
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-rejected-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-rejected-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Apr 23 20:02:41 2019
Return-Path: <eburger@standardstrack.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8705D120319 for <sipcore@ietfa.amsl.com>; Tue, 23 Apr 2019 20:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.689
X-Spam-Level: 
X-Spam-Status: No, score=-1.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.com
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 kOf_hVwk4blU for <sipcore@ietfa.amsl.com>; Tue, 23 Apr 2019 20:02:38 -0700 (PDT)
Received: from biz221.inmotionhosting.com (biz221.inmotionhosting.com [198.46.93.79]) (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 F2EB1120318 for <sipcore@ietf.org>; Tue, 23 Apr 2019 20:02:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=XkaVR8kNqyQQSdBJWWeJtsAkmrf6TvVfTRa92Wn5XkI=; b=nKwOs1k0UbUAzeBjt3XCLV3ye 5n7M5YK7wtEsFDR21fTO/Win8RO8fFWw109n/HVp1tM9CAp7hco9j4DPpCadynUu9qufCEWFVBULA RtO+eyYiE9ILINnsdzwcXIUwh6QnLULmNb+XcjkeUXyWL25m/x8/9cU0Q0KlmXhFddyAU=;
Received: from [68.100.196.217] (port=50484 helo=[192.168.10.26]) by biz221.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <eburger@standardstrack.com>) id 1hJ8Az-000iUl-Mb; Tue, 23 Apr 2019 20:02:36 -0700
From: Eric Burger <eburger@standardstrack.com>
Message-Id: <E66F06E5-4D2E-4FEE-88A4-446038743E26@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_968CCEB1-8EC0-4F96-811C-9688FAE6D682"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Tue, 23 Apr 2019 23:01:23 -0400
In-Reply-To: <2bed1f29-cf3e-e6df-60b8-590b88ab95d8@nostrum.com>
Cc: SIPCORE <sipcore@ietf.org>
To: Roach Adam <adam@nostrum.com>
References: <2bed1f29-cf3e-e6df-60b8-590b88ab95d8@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.8)
X-OutGoing-Spam-Status: No, score=-0.2
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz221.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/QzwJMPSp-S38MSSw8jZUTM2cko0>
Subject: Re: [sipcore] AD Review: draft-ietf-sipcore-rejected
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 03:02:40 -0000

--Apple-Mail=_968CCEB1-8EC0-4F96-811C-9688FAE6D682
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks for the review! I think the draft will read a lot easier. I=E2=80=99=
ve accepted all of your suggestions, with a sideways deflection of the =
first set of substantive issues. I=E2=80=99ll trim the rest of the =
comments as they are in the archive, and focus in-line on the first set =
of comments.

I just posted -07 and the announcement just flew by.
https://datatracker.ietf.org/doc/draft-ietf-sipcore-rejected/
Diff:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-rejected-07


> On Apr 17, 2019, at 9:41 PM, Adam Roach <adam@nostrum.com> wrote:
>=20
> This is my AD review for draft-ietf-sipcore-rejected. There are a few =
places
> where I think the mechanism needs to be better defined -- or, at =
least, more
> clearly described -- before it goes into IETF review. I've grouped =
those issues
> together at the top of my comments that follow.
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A74.1:
>=20
> This example is perplexing in a few dimensions that should be either
> changed or explained. These are confusing enough that I'd like to see =
a new
> version of the document before putting it into IETF last call.
>=20
> The first is that its Call-Info header field indicates a URL of the =
form:
>=20
>   https://block.example.net/complaint.json
>=20
> ...which strongly implies that one might find a JSON object at that =
location. It
> then goes on to specify that the thing one would retrieve from this =
location is
> a JWS. While there's nothing that technically binds a URL's name to =
the content
> type found at that URL, this goes against fairly well-established =
conventions in
> a way that is likely to confuse implementors.
>=20
> That would imply a change to:
>=20
>   https://block.example.net/complaint.jws

I would offer that when you resolve the URI, you will get=E2=80=A6 a =
JSON object. That JSON object /happens/ to be a JWS. Note that *.jws is =
a thing: we at BEA Systems (now Oracle) use it to identify Java Web =
Server code.

As such, no change there.

> But this leads us to the second problem: the form of the URL -- a =
domain
> followed by a simple word -- implies that this same URL is used for =
all
> rejected calls (and... one would assume is generated on the fly with a =
fresh
> "iat" parameter?)  If that's the case, then this URL becomes an oracle =
that
> allows for the exact kind of replay attacks described in the =
introduction. To
> prevent this from being such an oracle, it's going to minimally need =
to vary
> by call, which would lead it to look more like:
>=20
> =
https://block.example.net/79048YzkxNDA5NTI1MzA0OWFjOTFkMmFlODhiNTI2OWQ1ZTI=
.jws
>=20
> However, this takes us to yet a third problem, which is -- even with a
> JWS-per-rejected-call approach, nothing prevents an attacker from =
spoofing 608
> responses with this URL for as long as the "iat" is likely to be =
accepted by
> callers (probably on the order of minutes), which can still cause some =
pretty
> substantial damage.
>=20
> I *think* this requires the ability to bind the jCard-containing JWS =
to the
> call. This would require additional claims to be added to the body. =
You could
> re-use the "orig" and "dest" claims created by PASSPORT (but be wary =
of
> retargeting), or come up with your own claims that bind the rejection =
to the
> call (although be careful of choosing fields that may be fragile in =
the
> presence of B2BUAs); but I think the whole signing mechanism just =
doesn't work
> unless it's bound to the call in some way. It might be enough just to =
bind it to
> the calling party, since that reduces the attack from a DDoS to a =
simple
> one-device DoS.
>=20
> Note that this last problem doesn't really bear on the example itself; =
however,
> I wasn't completely convinced that it was an issue until I got to the =
example.

I do not think we need to bind the jCard to a specific call. I greatly =
expanded the language in the Security Considerations section to make it =
clear what threats we are mitigating by signing the jCard and including =
an iat claim. Specifically, it is not to prove that /this/ jCard belongs =
to /that/ call. It is to prove that /this/ signer signed /this/ jCard. =
And, in reality, most intermediaries will have a fixed jCard and will =
use the iat as a nonce. More verbosity in the Security Considerations. =
Let me know if it makes more sense.


> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A74.4, Figure 5:
>=20
> This is an issue that I'd like to see fixed before IETF last call.
>=20
> Please either show the use of PRACK with the 183 response, or indicate =
that the
> required PRACK messages have been elided from the diagram for clarity. =
In either
> case, this document must have RFC 3262 as a normative dependency, as =
it's
> impossible to satisfy its normatively-required behaviors without that
> mechanism.

Head smack given the major point of PRACK is to play announcements, says =
the guy who built announcement boxes <argh!>
Fixed.
Duh.
Thanks.


> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A76:
>=20
> This is an issue that I'd like to see fixed before IETF last call.
>=20
> The mechanism specifies that the JWS objects are required to contain =
an "iat"
> claim, but provides no guidance for how the recipient of such a JWS is =
supposed
> to use this information. Clearly, it's intended to be "fresh enough" =
to prevent
> replay attacks, but this is never stated.
>=20
> You should be able to fix this (once the first issue above is =
addressed) by
> adding something to the "Security Considerations" section modeled =
after
> https://tools.ietf.org/html/rfc8225#section-10.1

Done.


--Apple-Mail=_968CCEB1-8EC0-4F96-811C-9688FAE6D682
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIzBAEBCAAdFiEEfEc/N7T7IfiAuDEHDDCGh758rskFAly/0YMACgkQDDCGh758
rskrgQ//Qhdm98xs7VL/J0UpkFkL4S6cgexHz40/GhwfnidnstVf1WilWLk+YdNH
5/60CnCvhVg0Veuuh84oPK4RhIcDZ4kOuuCdLc21vriFI4ZeVdkGGAm6yl4/Hy4t
6sj/AMHpC94Cs8N14EE2goi7nRoC2ZdFPpOZjtf92hVfJAc9u5qa4mNgoErvF1rh
8C+vQfaMqvYjhtLQNg2OH8GAo/YznJa+bWt1JwTgcEuCgZS+tibulbRzPgMaziLg
YDjhISuOMoB8KFoBFqoEAxTVWYOQUGAgFpsci3G/N8drG2ysZwWlcTXa3C37NNr6
Vlg63ibty4hfK0me+A5AXTFRqhrU75UJ2vHjYH05ZB3PpVoEsTMt4Jxy5/M6wjny
9xLuc+CZNbcf9UYOOwxV835vFH1XimR5LBblKKuB51EEZuSJN4IrpnJKLiBECuJR
B1kZXWYPLfaY/Scgf4txACGMnQmtobnF3qXesP5+NStuVKEBuQW+jh23t0PcxFes
Y4hfhSZqF9qOHyR3De79MBMazh/xuZggglEx5hUYre/txAEr35CHR50a9BchdrMD
auAhYGaof1vjdAfF7Sd6rMKNRsUuhaMeiW183sHfpsXp5kn3st9EGTLmwWJvcSIQ
mTLFCkWdJolWf1ypVQ5OEp9N/8biU3FJLtHJO/AUQODonmUQbY8=
=d4zc
-----END PGP SIGNATURE-----

--Apple-Mail=_968CCEB1-8EC0-4F96-811C-9688FAE6D682--


From nobody Tue Apr 23 21:35:48 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4C91201B8 for <sipcore@ietfa.amsl.com>; Tue, 23 Apr 2019 21:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 eslVHGPWQEfP for <sipcore@ietfa.amsl.com>; Tue, 23 Apr 2019 21:35:44 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (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 57FEF12032A for <sipcore@ietf.org>; Tue, 23 Apr 2019 21:35:40 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x3O4Zc6e009496 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <sipcore@ietf.org>; Wed, 24 Apr 2019 00:35:39 -0400
To: sipcore@ietf.org
References: <155607397517.32461.8003402784805398777@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <8cd3e094-837c-621b-9eaa-c9abc3c770a4@alum.mit.edu>
Date: Wed, 24 Apr 2019 00:35:38 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <155607397517.32461.8003402784805398777@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/93rqepvLftDDAHRUbnP7IBMP2cE>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-rejected-07.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 04:35:47 -0000

A couple of nits:

Section 1:

s/service providers may not block/service providers may not be permitted 
to block/

(Otherwise it can be read as discretionary - might not block.)

Later in the section, the following:

    An algorithm can be vulnerable to an algorithm
    subject to the base rate fallacy

is very odd. (An algorithm is vulnerable to an algorithm?)
I don't know quite what was intended. Perhaps:


    An algorithm can be vulnerable to the base rate fallacy

Section 4.1:

s/One would construct the JWS would as follows./One would construct the 
JWS as follows./

	Thanks,
	Paul

