
From nobody Tue Sep  3 10:15:50 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 8F358120052 for <sipcore@ietfa.amsl.com>; Tue,  3 Sep 2019 10:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 c8WHLRYqLrv1 for <sipcore@ietfa.amsl.com>; Tue,  3 Sep 2019 10:15:46 -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 62E74120043 for <sipcore@ietf.org>; Tue,  3 Sep 2019 10:15:46 -0700 (PDT)
Received: from Kokiri.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 x83HFi6g026693 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <sipcore@ietf.org>; Tue, 3 Sep 2019 13:15:45 -0400
To: sipcore@ietf.org
References: <156722202781.25788.4683211146769372739@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <631148df-8105-c015-bbc1-4f44b6aa5db9@alum.mit.edu>
Date: Tue, 3 Sep 2019 13:15:44 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156722202781.25788.4683211146769372739@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/0Dg9cMj31tZQ8P0FOemdOiKkXTw>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-callinfo-spam-04.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: Tue, 03 Sep 2019 17:15:49 -0000

The first entry in the table in section 8.1 is messed up.

Otherwise looks good.

	Thanks,
	Paul

On 8/30/19 11:27 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           : SIP Call-Info Parameters for Labeling Calls
>          Author          : Henning Schulzrinne
> 	Filename        : draft-ietf-sipcore-callinfo-spam-04.txt
> 	Pages           : 11
> 	Date            : 2019-08-30
> 
> Abstract:
>     Called parties often wish to decide whether to accept, reject or
>     redirect calls based on the likely nature of the call.  For example,
>     they may want to reject unwanted telemarketing or fraudulent calls,
>     but accept emergency alerts from numbers not in their address book.
>     This document describes SIP Call-Info parameters and a feature tag
>     that allow originating, intermediate and terminating SIP entities to
>     label calls as to their type, confidence and references to additional
>     information.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sipcore-callinfo-spam-04
> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-callinfo-spam-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-callinfo-spam-04
> 
> 
> 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
> 


From nobody Fri Sep  6 02:16:44 2019
Return-Path: <jorgen.axell@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 67B6712006E for <sipcore@ietfa.amsl.com>; Fri,  6 Sep 2019 02:16:43 -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 Mras5jnjlv1w for <sipcore@ietfa.amsl.com>; Fri,  6 Sep 2019 02:16:41 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80047.outbound.protection.outlook.com [40.107.8.47]) (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 C782112001E for <sipcore@ietf.org>; Fri,  6 Sep 2019 02:16:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=he1/6Ym8ChCkJKRe70Q1xMLIqfk3DGfFYVpoepi1m2s6zbzMOnGLaa0caL9dBCZWxEcXmaZqSpHBV3ADyi1MxcpoJIHmW4Og5CDVYum4xNCIUwVvuapNJF7QZjm+LSctXqG6jDUPSSfvdznIQEOMgVwEuvCbbqzzratkAHzGQHqmK/MUHdD/p4RH8JyMMmSw3kK7+1oANeyZYe7r27W72gyENRnqB7N8oHKtkWeMPUnnXZv80WsM1XDepysXtTZ7kCd7LLmcZu3sd5tla7fO1B8Yqyv900vu9qbPSiqtsQPe+aLkmXQf6u5qot1EngMAaSPRUtCkMRwX8MgjlU8spg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wbZloREGDmBe7BaWXJeYdMPLcfP8273XTX7Uqu6I+jg=; b=IPjkVUFQ3ebxsP27MiZRHkzgSDPffcyOlz7NBHOkYYorMqq/EkclhjW2drYs/wi3bg7Tkduf8DCBA4YUdQFD+V7jjEEoR/TqbeAw/UmRaDGV225RbfeBTwMmyJpKeD5gMYyRI9iQG0Ysy2xGMx2wzpTrsgR0lmRwrV7JHseX6UUv/xFTXebWCdtNQH0ekxzWoOnetaOOhNEbbcuzGL6iOOgcLu2pXsWR8YDWE26nf1hwyMV19P7X3JdBK5EZPYScbQemuzy7jeJngvcHnlUpoOdQz7qQyuRgk8YQMHFRq3xLWI0qO+HKwCbEboflUrG6QUIxI06Mw8EqEpStu1XjMA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wbZloREGDmBe7BaWXJeYdMPLcfP8273XTX7Uqu6I+jg=; b=arviUzb7b1YvPf3Ul8OenjvY0dJWlj/2Jeo7t8yKAPhcFRonTMEsoDGPkBedbdAZbdXylbTgp+kZg4GY28lWYb5C94B32EhLRwjX+8F8tI23nzuTorwqQh/44sTpyhrmdh4Qj9rcec7uE05Ywi/ct4P8VibulHsJXJ/XCP97WYo=
Received: from HE1PR0701MB2220.eurprd07.prod.outlook.com (10.168.29.21) by HE1PR0701MB3036.eurprd07.prod.outlook.com (10.168.96.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.13; Fri, 6 Sep 2019 09:16:37 +0000
Received: from HE1PR0701MB2220.eurprd07.prod.outlook.com ([fe80::3d9e:1f7a:cf1f:b7ad]) by HE1PR0701MB2220.eurprd07.prod.outlook.com ([fe80::3d9e:1f7a:cf1f:b7ad%11]) with mapi id 15.20.2241.014; Fri, 6 Sep 2019 09:16:37 +0000
From: =?iso-8859-1?Q?J=F6rgen_Axell?= <jorgen.axell@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-callinfo-spam-04.txt
Thread-Index: AQHVX6wDL/mZy/lQjEuIXF9Y73fwHqcaNxgAgAQwFGA=
Date: Fri, 6 Sep 2019 09:16:37 +0000
Message-ID: <HE1PR0701MB222019C347BECAA3B575AEECE0BA0@HE1PR0701MB2220.eurprd07.prod.outlook.com>
References: <156722202781.25788.4683211146769372739@ietfa.amsl.com> <631148df-8105-c015-bbc1-4f44b6aa5db9@alum.mit.edu>
In-Reply-To: <631148df-8105-c015-bbc1-4f44b6aa5db9@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jorgen.axell@ericsson.com; 
x-originating-ip: [81.229.17.163]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e4cdbc25-4283-488a-4a5e-08d732aaeb8b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR0701MB3036; 
x-ms-traffictypediagnostic: HE1PR0701MB3036:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <HE1PR0701MB3036736C322348B98242A9A1E0BA0@HE1PR0701MB3036.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0152EBA40F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(39860400002)(376002)(136003)(346002)(189003)(199004)(13464003)(66946007)(229853002)(8676002)(1730700003)(81156014)(316002)(66476007)(76116006)(66446008)(6246003)(7736002)(6916009)(81166006)(74316002)(64756008)(66556008)(25786009)(53936002)(6306002)(6436002)(9686003)(66574012)(305945005)(55016002)(5640700003)(71190400001)(71200400001)(14444005)(256004)(3846002)(6116002)(52536014)(5660300002)(8936002)(45776006)(2906002)(66066001)(478600001)(446003)(14454004)(11346002)(966005)(476003)(2501003)(486006)(7696005)(76176011)(53546011)(2351001)(6506007)(26005)(186003)(102836004)(99286004)(86362001)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB3036; H:HE1PR0701MB2220.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: JSfNYdnSKUXViVziJy7xzhKzuvP2Aze5oVv7WwfIg+kZfgBAigt7RmQf8HFDoaBlaMm2OtRaYwChsGA4t7SJ8iZb3+ks9/AHKVm7OVJiENDwBoAudeGCAPLIk9EWmtMdIcPAP6MfOf7/k/2QBIJ9BGRqFp05NK+OPZq1kjU0qljdW+WYqJRZYiiqaLNp3XkjXGKj2YXWtnTKfrI1bYTppp3Pz9WbMmRWVotXiBt8CARNX1K3B872ZeUj6EZcMYwDThKIjTiZBldKMeVu0SMbYt/oE3xQ2gx/lxKNxtj2H97uxNUariSbQL4YyrAikeYpaVxNlsTu2+Dn5RpytwhTGsJY4gzq/cqZyTtaILlE6Jcff3ffE5OeECfVPw73679LuKwR7N+ffDK02X1mufXhT9zMVLBgizxUNBzoMpxHW/0=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e4cdbc25-4283-488a-4a5e-08d732aaeb8b
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2019 09:16:37.2688 (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-CrossTenant-userprincipalname: RTnxBf3Ous57OBnyYbDdNItYdEcSutbgAx6KXAf2xVsBVtjgJyNOqiq0c5Q+het+e2hsHOnxRboI4/UKGTryvUCSTnUScU50dosX+gF4u0w=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB3036
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/brbu7io8XL5TDqLWs8B6fhOJ33U>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-callinfo-spam-04.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: Fri, 06 Sep 2019 09:16:43 -0000

A minor question: The Feature-Capability indicator is named sip.call-info.s=
pam, while the heading of the doc is "SIP Call-Info Parameters for Labeling=
 Calls". Should the indicator be named similarly to be sip.call-info.labeli=
ng?

Regards,
J=F6rgen

-----Original Message-----
From: sipcore <sipcore-bounces@ietf.org> On Behalf Of Paul Kyzivat
Sent: den 3 september 2019 19:16
To: sipcore@ietf.org
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-callinfo-spam-04.txt

The first entry in the table in section 8.1 is messed up.

Otherwise looks good.

	Thanks,
	Paul

On 8/30/19 11:27 PM, internet-drafts@ietf.org wrote:
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Session Initiation Protocol Core WG of t=
he IETF.
>=20
>          Title           : SIP Call-Info Parameters for Labeling Calls
>          Author          : Henning Schulzrinne
> 	Filename        : draft-ietf-sipcore-callinfo-spam-04.txt
> 	Pages           : 11
> 	Date            : 2019-08-30
>=20
> Abstract:
>     Called parties often wish to decide whether to accept, reject or
>     redirect calls based on the likely nature of the call.  For example,
>     they may want to reject unwanted telemarketing or fraudulent calls,
>     but accept emergency alerts from numbers not in their address book.
>     This document describes SIP Call-Info parameters and a feature tag
>     that allow originating, intermediate and terminating SIP entities to
>     label calls as to their type, confidence and references to additional
>     information.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sipcore-callinfo-spam-04
> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-callinfo-spam
> -04
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-callinfo-spam-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>=20

_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore


From nobody Sun Sep  8 19:09:54 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 35574120047; Sun,  8 Sep 2019 19:09:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-sipcore-callinfo-spam.all@ietf.org, sipcore@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Joel Halpern <jmh@joelhalpern.com>
Message-ID: <156799498109.25390.17063977634118014127@ietfa.amsl.com>
Date: Sun, 08 Sep 2019 19:09:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Ivss6gtQc3Jd7iAUx-RmzALWivk>
Subject: [sipcore] Genart last call review of draft-ietf-sipcore-callinfo-spam-04
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, 09 Sep 2019 02:09:42 -0000

Reviewer: Joel Halpern
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-sipcore-callinfo-spam-04
Reviewer: Joel Halpern
Review Date: 2019-09-08
IETF LC End Date: 2019-09-14
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed Standard RFC

Major issues: N/A

Minor issues:
    ID Nits and inspection of the txt show that the ABNF is formatted with
    lines that are too long.  While I expect that the RFC Editor can fix this,
    it seems safer for the authors to do the repairs themselves.  (The shepherd
    has indicated they will be fixed, so I am merely including this here to
    make sure it is not forgotten.)

Nits/editorial comments:  N/A



From nobody Mon Sep  9 06:22:49 2019
Return-Path: <R.Jesske@telekom.de>
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 B8D741201CE for <sipcore@ietfa.amsl.com>; Mon,  9 Sep 2019 06:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level: 
X-Spam-Status: No, score=-4.298 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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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=telekom.de
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 FWZ_VlOwNKkS for <sipcore@ietfa.amsl.com>; Mon,  9 Sep 2019 06:22:46 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 A651A120164 for <sipcore@ietf.org>; Mon,  9 Sep 2019 06:22:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1568035359; x=1599571359; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=J+0vcA3448neMhwXyE4rbWK2ZzSMkTm0blBu56M6qSs=; b=6GxribiE7FEZU/nNnvCFWcijSCrSXJJakdxzk/3dGQQAsj1WGcCyPiPb scA2f3hTJl0ytJaQdxmLsT8k0FSSA93jeUQMewIjomDQqZv9uc8rrT1O7 +XvPHfxCNWqCR8oD37GNuYVtzCEoBBfaamqg2tsngZNlikHSQMOJLdOEf kZ1oww7I+XVK+Qm1IN4KKWSScPXgXIygT8wvy14mG7pV/DIJIcJH3X2sL BYJaBtFwBc32dRynaOSv5onrEnFyFz67ANRoaqOiGVQfvMPsnbtSX+rh9 CS35kwlEW+Pr/H6NUc+egUuKCfT/CAHYc0qKybN0YMkXktvUm1W43H8Rg Q==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Sep 2019 15:22:35 +0200
X-IronPort-AV: E=Sophos;i="5.64,484,1559512800"; d="scan'208";a="358930968"
X-MGA-submission: =?us-ascii?q?MDEkHNTFG9V4rfBE9LHXwhwyy/Q40NHixcniT1?= =?us-ascii?q?n3mmPIVsaLEvTQkq63EfVJwVwvtcFM2sJgXuKCZwtpplMG9cnumDBW6y?= =?us-ascii?q?FjbdHL5tASWqovo8L3l0dd0pp+mfkKWPLRACa9qNNhgGvNPLtPEDytQE?= =?us-ascii?q?21xFZil1R9K4Ltd49q3B53Bg=3D=3D?=
Received: from he105867.emea1.cds.t-internal.com ([10.169.119.44]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 09 Sep 2019 15:22:39 +0200
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE105867.emea1.cds.t-internal.com (10.169.119.44) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 9 Sep 2019 15:22:22 +0200
Received: from HE100181.emea1.cds.t-internal.com (10.171.40.15) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 9 Sep 2019 15:22:22 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.23) by O365mail02.telekom.de (172.30.0.235) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 9 Sep 2019 15:22:24 +0200
Received: from FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE (10.158.154.143) by FRXPR01MB0264.DEUPRD01.PROD.OUTLOOK.DE (10.158.151.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.18; Mon, 9 Sep 2019 13:22:22 +0000
Received: from FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE ([fe80::b4bc:4fd2:ed4e:e839]) by FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE ([fe80::b4bc:4fd2:ed4e:e839%3]) with mapi id 15.20.2241.018; Mon, 9 Sep 2019 13:22:22 +0000
From: <R.Jesske@telekom.de>
To: <rjsparks@nostrum.com>, <mahoney@nostrum.com>, <sipcore@ietf.org>
Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-locparam
Thread-Index: AQHVU6HhngipEylhAEmT4aqvpcC40qcSS82AgBDVaTA=
Date: Mon, 9 Sep 2019 13:22:21 +0000
Message-ID: <FRXPR01MB0743498A164A03CF567F5B1DF9B70@FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE>
References: <ee8b0ec3-a33b-bfc1-35f4-fb35a8fd01f7@nostrum.com> <da702c91-f130-3f4f-c89f-6551c0584856@nostrum.com>
In-Reply-To: <da702c91-f130-3f4f-c89f-6551c0584856@nostrum.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=R.Jesske@telekom.de; 
x-originating-ip: [164.19.4.107]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cba19ffb-d0e5-4b52-752b-08d73528bf50
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:FRXPR01MB0264; 
x-ms-traffictypediagnostic: FRXPR01MB0264:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <FRXPR01MB0264614116ABC9A90D3A1410F9B70@FRXPR01MB0264.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01559F388D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(366004)(396003)(136003)(39860400002)(53754006)(189003)(199004)(66556008)(66476007)(66946007)(14454004)(8676002)(52396003)(66066001)(8936002)(6116002)(86362001)(2906002)(5660300002)(53546011)(316002)(64756008)(66446008)(3846002)(76176011)(256004)(81166006)(14444005)(102836004)(478600001)(81156014)(110136005)(26005)(9686003)(446003)(11346002)(6306002)(71200400001)(71190400001)(7736002)(76116006)(7696005)(186003)(305945005)(966005)(33656002)(66574012)(486006)(476003)(55016002)(53936002); DIR:OUT; SFP:1101; SCL:1; SRVR:FRXPR01MB0264; H:FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: dDRYnMNFc3ZzhPffl4gQ7TfoDSIS6i8weYoLmKuIU7Ug7dU3K1Wpg5OkCwa/oJDagQ4W078H5LgT47fbcgQo7mSSF4O1hdbkJxz4+7Yyw3NoJ+B78puAE0RxuQSxz4E3e3Yd1MxvoxSW70+44QuIhgjf2nHk7Z/UJM7evnZEQptnLoPJ4mGq12UnGMuRTIG35m3hiK89s1T1AaSi3M1/AniVemnp2XUlBnSvgvaXezKM08xFQDEJGNPLDx8V6ietiGmTFlESSdCcYRSRDfVgP+jddT+Xh39qbSSwwea7qOhtTxX2EdCa/AVZAZQSj8vJf7lGEJzdwDLZF2AeBGHoNhlYI3loLoELE+ctVb+ACFObCd1rPYTPm9qxoygQHxOR4B+I3TPL4XNjSn6SuAv+ig4luMqY8NPMC2o3sdOZo1g=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cba19ffb-d0e5-4b52-752b-08d73528bf50
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Sep 2019 13:22:21.7741 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: FDgNZPsSjBvF1PjbUTg6fD0yxz2e98Qv7+G5n6LyjXP7y7D+0q5ptIY1gY/htbY9CPVrxziSD7IpWzNafPwrhQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRXPR01MB0264
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/hgYcbdWOduY47-Cw_ArzHoTdgdk>
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-locparam
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, 09 Sep 2019 13:22:49 -0000

SGkgUm9iZXJ0LA0KdGhhbmsgeW91IGZvciB5b3VyIGNvbW1lbnRzLiBBbmQgc29ycnkgZm9yIHRo
ZSBkZWxheSBpbiBhbnN3ZXJpbmcuDQoNCkhlcmUgYXJlIG15IHByb3Bvc2FscyB0byB5b3VyIGNv
bW1lbnRzOg0KDQoxLiBJIHRoaW5rIHRoaXMgZ2V0cyBhbG9uZyB3aXRoIENocmlzdGVycyBjb21t
ZW50cyBoZSBoYWQuDQoNClNvIEkgY2hhbmdlZDoNCj4gICAiVGhlIFNJUCBnZW9sb2NhdGlvbiBz
cGVjaWZpY2F0aW9uIFtSRkM2NDQyXSBkZXNjcmliZXMgdGhlDQo+ICAgIkdlb2xvY2F0aW9uIiBT
SVAgaGVhZGVyIGZpZWxkIHdoaWNoIGlzIHVzZWQgdG8gaW5kaWNhdGUgdGhhdCB0aGUgU0lQDQo+
ICAgbWVzc2FnZSBpcyBjb252ZXlpbmcgbG9jYXRpb24gaW5mb3JtYXRpb24uICBUaGUgc3BlY2lm
aWNhdGlvbg0KPiAgIHN1Z2dlc3RzIHRoYXQgb25seSBvbmUgbG9jYXRpb24gdmFsdWUgc2hvdWxk
IGJlIGNvbnZleWVkLiINCg0KVG86DQo+ICAgIlRoZSBTSVAgZ2VvbG9jYXRpb24gc3BlY2lmaWNh
dGlvbiBbUkZDNjQ0Ml0gZGVzY3JpYmVzIHRoZSAgICJHZW9sb2NhdGlvbiIgU0lQIGhlYWRlciBm
aWVsZCB3aGljaCBpcyB1c2VkIHRvIGluZGljYXRlIHRoYXQgdGhlIFNJUA0KPiAgIG1lc3NhZ2Ug
aXMgY29udmV5aW5nIGxvY2F0aW9uIGluZm9ybWF0aW9uLiAgDQo+ICJUaGUgc3BlY2lmaWNhdGlv
biBzcGVjaWZpZXMgdGhhdCBTSVAgaW50ZXJtZWRpYXJpZXMgc2hvdWxkIG5vdCBhZGQgbG9jYXRp
b24gdmFsdWVzIHRvIGEgU0lQIHJlcXVlc3QgdGhhdCBhbHJlYWR5IGNvbnRhaW5zIGxvY2F0aW9u
IHZhbHVlLiINCg0KSW4gYWRkaXRpb24gSSBjYW4gYWRkIHRoZSBzZW50ZW5jZToNCltSRkM2NDQy
XSBhbHNvIHN0YXRlcyB0aGF0IGlmIGEgU0lQIGludGVybWVkaWFyeSBhZGRzIGxvY2F0aW9uIGl0
IGlzIGZ1bGx5IHJlc3BvbnNpYmxlIGZvciBhZGRyZXNzaW5nIHRoZSBjb25jZXJucyBvZiBhbnkN
CiAgIDQyNCAoQmFkIExvY2F0aW9uIEluZm9ybWF0aW9uKSBTSVAgcmVzcG9uc2UgaXQgcmVjZWl2
ZXMuDQoNCldvdWxkIHRoaXMgT0sgZm9yIHlvdT8NCg0KMjoNCkkgdGhpbmsgdGhpcyBpcyBhIGxl
ZnQgb3ZlciBmcm9tIHNvbWUgY2hhbmdlcyBvZiB0aGUgcGFzdC4gSXQgaXMgb25seSBzYXlpbmcg
dGhhdCBpbiB0aGUgY2FzZSB3ZSBkbyBub3QgbmVlZCBhbmF5IGxvY2F0aW9uIHRvIGFsbG9jYXRl
IHRoZSBlbWVyZ2VuY3kgY2FsbCB0aGVuIHdlIGRvIGFsc28gbm90IG5lZWQgYW55IGxvY2F0aW9u
LXNvdXJjZSBwYXJhbWV0ZXIuDQpPbGQgVGV4dDoNClRoZSBsb2NhdGlvbi1zb3VyY2UgcGFyYW1l
dGVyIGlzIG5vdCBpbmNsdWRlZCBpbiBhIFNJUCBtZXNzYWdlDQogICAgICAgICBzZW50IHRvIGFu
b3RoZXIgbmV0d29yayBpZiB0aGVyZSBpcyBubyB0cnVzdCByZWxhdGlvbnNoaXAuICBUaGUNCiAg
ICAgICAgIFRoZSBsb2NhdGlvbi1zb3VyY2UgcGFyYW1ldGVyIGlzIG5vdCBhcHBsaWNhYmxlIGlm
IHRoZSBhZG1pbmlzdHJhdGl2ZSBkb21haW4gbWFuYWdlcw0KICAgICAgICAgZW1lcmdlbmN5IGNh
bGxzIGluIGEgd2F5IHRoYXQgZG9lcyBub3QgcmVxdWlyZSBsb2NhdGlvbiBzb3VyY2UgZ2VuZXJh
dGluZyB0aGUgbG9jYXRpb24uDQoNClByb3Bvc2VkIFRleHQ6DQpUaGUgbG9jYXRpb24tc291cmNl
IHBhcmFtZXRlciBpcyBub3QgaW5jbHVkZWQgaW4gYSBTSVAgbWVzc2FnZQ0KICAgICAgICAgc2Vu
dCB0byBhbm90aGVyIG5ldHdvcmsgaWYgdGhlcmUgaXMgbm8gdHJ1c3QgcmVsYXRpb25zaGlwLiAg
VGhlDQogICAgICAgICBUaGUgbG9jYXRpb24tc291cmNlIHBhcmFtZXRlciBpcyBub3QgYXBwbGlj
YWJsZSBpZiB0aGUgYWRtaW5pc3RyYXRpdmUgZG9tYWluIG1hbmFnZXMNCiAgICAgICAgIGVtZXJn
ZW5jeSBjYWxscyBpbiBhIHdheSB0aGF0IGRvZXMgbm90IHJlcXVpcmUgYW55ICBnZW5lcmF0aW9u
IG9mIHRoZSBsb2NhdGlvbi4NCg0KMy4gDQpUaGlzIGRvY3VtZW50IGRvZXMgbm90IGFkZCBhbnkg
ZnVydGhlciBiZWhhdmlvciBvbiBwcml2YWN5IHNpbmNlIHdlIGFyZSBhZGRpbmcgYW4gYWRkaXRp
b25hbCBwYXJhbWV0ZXIgdG8gdGhlIGdlby1wcml2IGhlYWRlci4NClRoZSBmYWN0IGlzIHRoYXQg
d2UgaGF2ZSByZXF1aXJlbWVudHMgb24gZW1lcmdlbmN5IGNhbGxpbmcgZGVwZW5kZWQgb24gcmVn
dWxhdG9yaWx5IHJ1bGVzLg0KU28gc2VlbiBmcm9tIHRoaXMgdGhlIGZhY3QgdGhhdCBhIGxvY2F0
aW9uIGlzIHNlbnQgdG93YXJkcyB0aGUgUFNBUCBpcyBiYXNlZCBvbiB0aGVzZSBydWxlcy4NCldl
IGhhdmUgYWxzbyBhIGxvdCBvZiB3b3JkcyByZWdhcmRpbmcgcHJpdmFjeSBydWxpbmcgYmFzZWQg
b24gYWNjZXNzIGFuZCBsb2NhdGlvbiBzZXJ2aWNlIHdpdGhpbiBSRjYyODAgd2hlcmUgUkZDNjQ0
MiBpcyBhbHNvIHJlZmVycmluZyB0by4NCkZyb20gbXkgcG9pbnQgb2YgdmlldyBSRkM2NDQyIGlz
IGFscmVhZHkgZGVzY3JpYmluZyBldmVyeXRoaW5nLg0KDQpTbyB3b3VsZCB5b3UgbGlrZSB0byBz
ZWUgZXZlcnl0aGluZyByZXBlYXRlZD8gT3IgaXMgdGhlcmUgYW55IHNwZWNpZmljIHdoYXQgd2Ug
bmVlZHMgdG8gdGFrZSBpbnRvIGNvbnNpZGVyYXRpb24gd2hhdCBJIG1pc3NlZD8NCg0KVGhhbmsg
eW91IGFuZCBCZXN0IFJlZ2FyZHMNCg0KUm9sYW5kDQoNCi0tLS0tVXJzcHLDvG5nbGljaGUgTmFj
aHJpY2h0LS0tLS0NClZvbjogc2lwY29yZSA8c2lwY29yZS1ib3VuY2VzQGlldGYub3JnPiBJbSBB
dWZ0cmFnIHZvbiBSb2JlcnQgU3BhcmtzDQpHZXNlbmRldDogRG9ubmVyc3RhZywgMjkuIEF1Z3Vz
dCAyMDE5IDE2OjU0DQpBbjogQS4gSmVhbiBNYWhvbmV5IDxtYWhvbmV5QG5vc3RydW0uY29tPjsg
U0lQQ09SRSA8c2lwY29yZUBpZXRmLm9yZz4NCkJldHJlZmY6IFJlOiBbc2lwY29yZV0gV0dMQzog
ZHJhZnQtaWV0Zi1zaXBjb3JlLWxvY3BhcmFtDQoNCkEgZmV3IGNvbW1lbnRzOg0KDQpJIGRpc2Fn
cmVlIHRoYXQgNjQ0MiAic3VnZ2VzdHMgdGhhdCBvbmx5IG9uZSBsb2NhdGlvbiB2YWx1ZSBzaG91
bGQgYmUgY29udmV5ZWQiLiA2NDQyIGRvZXNuJ3Qgc2F5IHRoYXQgYXQgYWxsLiBJdCBzYXlzIGlm
IHlvdSBhZGQgYWRkaXRpb25hbCB0aGluZ3MsIHlvdSBiZWNvbWUgcmVzcG9uc2libGUgZm9yIHdo
YXQgdGhleSBtZWFuIGFuZCBob3cgdGhleSdyZSB1c2VkIChTZWUgdGhlICJ5b3UgYnJlYWsgaXQs
IHlvdSBib3VnaHQgaXQiIGRpc2N1c3Npb24pLiBJIHN1Z2dlc3QgdGhpcyBwYXJ0IG9mIHRoZSBp
bnRyb2R1Y3Rpb24gYmUgcmVwaHJhc2VkIHRvIGFjY3VyYXRlbHkgcmVmbGVjdCB3aGF0IDY0NDIg
c2F5cy4NCg0KSW4gU2VjdGlvbiAzLCBUaGlzIHNlbnRlbmNlOiAiVGhlIFRoZSBsb2Mtc3JjIHBh
cmFtZXRlciBpcyBub3QgYXBwbGljYWJsZSBpZiB0aGUgYWRtaW5pc3RyYXRpdmUgZG9tYWluIG1h
bmFnZXMgZW1lcmdlbmN5IGNhbGxzIGluIGEgd2F5IHRoYXQgZG9lcyBub3QgcmVxdWlyZSBsb2Nh
dGlvbiBzb3VyY2UgZ2VuZXJhdGluZyB0aGUgbG9jYXRpb24iIGhhcyBhIHJlcGVhdGVkICJUaGUi
IGFuZCBkb2VzIG5vdCBwYXJzZS4gV2hhdCBkb2VzICJyZXF1aXJlIGxvY2F0aW9uIHNvdXJjZSBn
ZW5lcmF0aW5nIHRoZSBsb2NhdGlvbiIgbWVhbj8NCg0KVGhlIHByaXZhY3kgY29uc2lkZXJhdGlv
bnMgc2VjdGlvbiBzaG91bGQgc2F5IG1vcmUgYWJvdXQgdGhlICJwcml2IiBwYXJ0IG9mIGdlb3By
aXYuIEEgcGVyc29uIHByb3ZpZGluZyBhIGxvY2F0aW9uIHdpdGggZ2VvcHJpdiBnZXRzIHRvIHNw
ZWNpZnkgcG9saWN5IGZvciB0aGUgdXNlIG9mIGEgbG9jYXRpb24gaW4gYWRkaXRpb24gdG8gdGhl
IGxvY2F0aW9uLiBBcyA2NDQyIHRyaWVzIHRvIHBvaW50IG91dCwgYSBtaWRkbGVib3ggYWRkaW5n
IGxvY2F0aW9uIGNhbid0IF9rbm93XyB0aGUgcGVyc29uJ3Mgd2lzaGVzLCBhbmQgY2FuIG9ubHkg
dW5pbGF0ZXJhbGx5IGFwcGx5IGl0cyBvd24gcHJpdmFjeSBwb2xpY2llcy4gRm9yIGVtZXJnZW5j
eSBjYWxsaW5nLCBJIGtub3cgYWJvdXQgdGhlIGFyZ3VtZW50IHRoYXQgcmVsaWVzIG9uIGFuIGlt
cGxpY2l0IGFncmVlbWVudCBhc3N1bWluZyB0aGF0IHRoZSB1c2VyIHdvdWxkIF93YW50XyB0aGVp
ciBsb2NhdGlvbiBjb252ZXllZC7CoCBCdXQgdGhlIGRvY3VtZW50IGlzIGN1cnJlbnRseSBzaWxl
bnQgb24gdGhpcy4gSXQgc2hvdWxkIGJlIGV4cGxpY2l0LiBUaGUgY2xhaW0gdGhhdCB0aGlzIGJl
aGF2aW9yIGRvZXNuJ3QgY2hhbmdlIHRoZSBwcml2YWN5IGNvbnNpZGVyYXRpb25zIGluIDY0NDIg
aXMgYSBsaXR0bGUgZWRneS4NCg0KUmpTDQoNCk9uIDgvMTUvMTkgMjo0MyBQTSwgQS4gSmVhbiBN
YWhvbmV5IHdyb3RlOg0KPiBIaSBhbGwsDQo+DQo+IFRoaXMgYmVnaW5zIHRoZSBXb3JraW5nIEdy
b3VwIExhc3QgQ2FsbCBvZiBkcmFmdC1pZXRmLXNpcGNvcmUtbG9jcGFyYW0gDQo+IChMb2NhdGlv
biBTb3VyY2UgUGFyYW1ldGVyIGZvciB0aGUgU0lQIEdlb2xvY2F0aW9uIEhlYWRlciBGaWVsZCku
DQo+DQo+IFBsZWFzZSBwb3N0IGFueSBmZWVkYmFjayB0byB0aGUgc2lwY29yZSBtYWlsaW5nIGxp
c3QgYnkgRnJpZGF5LCBBdWd1c3QgDQo+IDMwLg0KPg0KPiBodHRwczovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1pZXRmLXNpcGNvcmUtbG9jcGFyYW0vDQo+DQo+IFRoYW5rcyENCj4N
Cj4gSmVhbg0KPg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPiBzaXBjb3JlIG1haWxpbmcgbGlzdA0KPiBzaXBjb3JlQGlldGYub3JnDQo+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwY29yZQ0KDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kc2lwY29yZSBtYWlsaW5nIGxpc3QN
CnNpcGNvcmVAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
c2lwY29yZQ0K


From nobody Thu Sep 12 19:05:05 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 753461201A3; Thu, 12 Sep 2019 19:04:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nagendra Kumar via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: draft-ietf-sipcore-callinfo-spam.all@ietf.org, sipcore@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Nagendra Kumar <naikumar@cisco.com>
Message-ID: <156834028538.16481.16157896877930138059@ietfa.amsl.com>
Date: Thu, 12 Sep 2019 19:04:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/2pymrGOWo1v3THVDrWdU2Y0gRus>
Subject: [sipcore] Opsdir last call review of draft-ietf-sipcore-callinfo-spam-04
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: Fri, 13 Sep 2019 02:04:45 -0000

Reviewer: Nagendra Kumar
Review result: Has Nits

Quick Summary:

The draft proposes new Call-Info Header fields to label the type/nature of the
call.

Overall the draft appears to be well written. There are some nits as defined in
the GenArt.  In addition to those nits, the below text in IANA section seems
incorrect and the order should be changed:

    +--------------+----------------+-------------------+------------+
    | Header Field | Parameter Name | Predefined Values | Reference  |
    +--------------+----------------+-------------------+------------+
    | [this RFC]   | Call-Info      | confidence        | No         |

I don't have any other concerns or comments in terms of the operational aspects
of this draft.

Thanks,
Nagendra


From nobody Sun Sep 15 11:32:55 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 031211200B7 for <sipcore@ietfa.amsl.com>; Sun, 15 Sep 2019 11:32:54 -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 3HijXViwwXvB for <sipcore@ietfa.amsl.com>; Sun, 15 Sep 2019 11:32:52 -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 5D72012008F for <sipcore@ietf.org>; Sun, 15 Sep 2019 11:32:52 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x8FIWnqS042807 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <sipcore@ietf.org>; Sun, 15 Sep 2019 13:32:50 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1568572370; bh=m4DCRd6fJUjNNvF4g61XnDSiRDa1btv6a8rhd/Y7oPg=; h=To:From:Subject:Date; b=G+XfGNnAwH/TQeodStH3+taE7P9XCL+NAxAzSjWOH6ABvt6Ehqz34Yeg+4V5aPUVP x+3YHJcOL5MLHVks9snzgJJ1BL3rAweLyBRYf3aCjdQM5P4UzyccuacQ9yEFyTsQpW XxUr8Kp1fiehCNuAYksQiDG2uXIGLkz+LuWxLvlg=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be mutabilis-2.local
To: SIPCORE <sipcore@ietf.org>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <bc15fc96-201a-fefd-8840-b4121d2c67b2@nostrum.com>
Date: Sun, 15 Sep 2019 13:32:49 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.9.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/dVPBK3FtZPQs53tDZAmFoQnIYyE>
Subject: [sipcore] sipcore meeting at IETF 106?
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, 15 Sep 2019 18:32:54 -0000

Hi all,

If you have a topic you would like to present at IETF 106 in Singapore, 
please let the chairs know by Sept 30.

IETF 106 important dates:
https://datatracker.ietf.org/meeting/106/important-dates/

Thanks!

Jean


From nobody Mon Sep 16 01:24:39 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 655CE12003F; Mon, 16 Sep 2019 01:24:38 -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.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <156862227833.28094.16490657369827918572@ietfa.amsl.com>
Date: Mon, 16 Sep 2019 01:24:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/aFnuKDrd018dDqJ0JW81PxGKWsU>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-locparam-03.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: Mon, 16 Sep 2019 08:24:38 -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           : Location Source Parameter for the SIP Geolocation Header Field
        Authors         : James Winterbottom
                          Roland Jesske
                          Bruno Chatras
                          Andrew Hutton
	Filename        : draft-ietf-sipcore-locparam-03.txt
	Pages           : 8
	Date            : 2019-09-16

Abstract:
   There are some circumstances where a Geolocation header field may
   contain more than one location value.  Knowing the identity of the
   node adding the location value allows the recipient more freedom in
   selecting the value to look at first rather than relying solely on
   the order of the location values.  This document defines the
   location-source parameter so that the entity adding the location
   value to Geolocation header field can identify itself using its
   hostname.


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

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

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


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 Mon Sep 16 01:30:50 2019
Return-Path: <R.Jesske@telekom.de>
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 B149E120825 for <sipcore@ietfa.amsl.com>; Mon, 16 Sep 2019 01:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 URlQSMiEv99o for <sipcore@ietfa.amsl.com>; Mon, 16 Sep 2019 01:30:45 -0700 (PDT)
Received: from mailout11.telekom.de (mailout11.telekom.de [194.25.225.207]) (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 16F2412081C for <sipcore@ietf.org>; Mon, 16 Sep 2019 01:30:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1568622631; x=1600158631; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=z73qm+IIlXSKkthvgqdEEjvBCwLPvwnJJCKAKbFimOI=; b=rSfBWqZ4Yz4z9xSZRKM7b5o7VCW3FqOa9EE5N3ahLsSjMVV3oazoezNk 08N2+HSTO9A9OFmW688qU7BWiC93JJXQnKO5H7+mRAl3jBvFaILcptTG4 hFTT1dEJnFi3rhIRPda0CwzO3ZJedJi8cyliNiMCnvb9Hx9nRvxuAD/BL nqXsQZFCxuD8RqyZnAjWVh16qYuQNPHx0dTKoHSMDRq/eZCSJtL8034X1 rpHfFb3Z+PcnGpYIo+G7KuejaqgeHcugUC48vpq0gcR2VLJHrAPsisvfN C9vFNMUqQYjeOqVHuCjXW/Iqk4eImSQCJwYbabOi5FJDHISDFvY+WNI+u w==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT11.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Sep 2019 10:30:28 +0200
X-IronPort-AV: E=Sophos;i="5.64,512,1559512800"; d="scan'208";a="363126506"
X-MGA-submission: =?us-ascii?q?MDGJgUg2txngyvgzq9SW1Du+ZQnFpYravP/kR2?= =?us-ascii?q?R55n556GhRpu8k4MMskBggP9wg1rWdCb1w/QHlOZJ6fwdzGaUjTWfYdg?= =?us-ascii?q?TWOl5wySANRKzz0wwzZO1DSRSwtMz+5G1osGko9mI7CDZzLAj3W9WbVA?= =?us-ascii?q?oXdRZTAVH97pjs01VVKLMwUw=3D=3D?=
Received: from he105715.emea1.cds.t-internal.com ([10.169.118.51]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 16 Sep 2019 10:30:37 +0200
Received: from HE105715.EMEA1.cds.t-internal.com (10.169.118.51) by HE105715.emea1.cds.t-internal.com (10.169.118.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 16 Sep 2019 10:30:36 +0200
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE105715.EMEA1.cds.t-internal.com (10.169.118.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 16 Sep 2019 10:30:36 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.19) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 16 Sep 2019 10:30:34 +0200
Received: from FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE (10.158.154.143) by FRXPR01MB0536.DEUPRD01.PROD.OUTLOOK.DE (10.158.153.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.23; Mon, 16 Sep 2019 08:30:35 +0000
Received: from FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE ([fe80::b4bc:4fd2:ed4e:e839]) by FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE ([fe80::b4bc:4fd2:ed4e:e839%3]) with mapi id 15.20.2263.023; Mon, 16 Sep 2019 08:30:35 +0000
From: <R.Jesske@telekom.de>
To: <mahoney@nostrum.com>, <sipcore@ietf.org>
Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-locparam
Thread-Index: AQHVU6HhngipEylhAEmT4aqvpcC40qcBNX+AgCzz53A=
Date: Mon, 16 Sep 2019 08:30:35 +0000
Message-ID: <FRXPR01MB07430C0666624B68EF9C04B1F98C0@FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE>
References: <ee8b0ec3-a33b-bfc1-35f4-fb35a8fd01f7@nostrum.com> <89ad49a5-1a2e-d408-91f0-e12e40749b2e@nostrum.com>
In-Reply-To: <89ad49a5-1a2e-d408-91f0-e12e40749b2e@nostrum.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=R.Jesske@telekom.de; 
x-originating-ip: [164.19.3.245]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 51fdbe69-c353-4bcc-0e5a-08d73a8025b4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:FRXPR01MB0536; 
x-ms-traffictypediagnostic: FRXPR01MB0536:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <FRXPR01MB0536B5721D3CE16B5F557D88F98C0@FRXPR01MB0536.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0162ACCC24
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(136003)(376002)(396003)(346002)(199004)(189003)(53754006)(66476007)(66556008)(81156014)(52396003)(8676002)(102836004)(53936002)(71190400001)(64756008)(76116006)(8936002)(33656002)(81166006)(26005)(478600001)(305945005)(76176011)(66946007)(2501003)(53546011)(7696005)(66446008)(476003)(446003)(11346002)(55016002)(186003)(9686003)(66574012)(5660300002)(66066001)(7736002)(71200400001)(86362001)(256004)(486006)(6306002)(14454004)(316002)(413944005)(3846002)(6116002)(110136005)(2906002)(966005); DIR:OUT; SFP:1101; SCL:1; SRVR:FRXPR01MB0536; H:FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ROYzt4EXHGMoHFhw0VW56OXhx6ZSvtXuelchsnctqL5am9/2R1Kowp5D81TPWO3sr79ZjB/xst16WzX+m1m+KbYzR5ibU4YAb63s885bJc8Fo4NpUs7x78vbfXguJ/XQHYo7twqfw+Rjk+n+q3Su7mqLQrM6OFyR+Pbbe1hZD4PlubEU97xWyAarCqFVqOiCEimpeY67jr/hnMtHCYg3WQCp75ZAMF/UiKcvMkdtao22SmhAQCnNg3yPrIuljahQeQx8gQZoJUq7fYRaTl/bFRnxfmkingmc0JM0NLwlH6PWxymE4gSkehuZhbs42LPdO0jjR3dFS1lTD3d8Wn0N/5C7GyhVWDVZUJKhRWTGgFTFPbqEn+wTcl6KizAElBRLtaQm+zr+yJzH4FsLDnOO+YqSfkvypTI11jn0S5vPjlE=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 51fdbe69-c353-4bcc-0e5a-08d73a8025b4
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Sep 2019 08:30:35.8186 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ayEgcrXfR0dXzE0XrKtwrqOcDas/U3QIdfhUUhwnfLWwC1ldxtfdWgm2+99kxB449xsoh5vm3iby/bfrCuwCdQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRXPR01MB0536
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/VUWLM3n1aaLHhsbljL58Q5Cbkoo>
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-locparam
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, 16 Sep 2019 08:30:48 -0000

Dear all,
thank you for reviewing the draft and giving comments.
After the end of WGLC I have now uploaded a new draft which reflects all co=
mments and proposals given over the last weeks.
You can check the changes under URL:            https://www.ietf.org/intern=
et-drafts/draft-ietf-sipcore-locparam-03.txt

Thank you and Best Regards

Roland


-----Urspr=FCngliche Nachricht-----
Von: sipcore <sipcore-bounces@ietf.org> Im Auftrag von A. Jean Mahoney
Gesendet: Sonntag, 18. August 2019 19:57
An: sipcore@ietf.org
Betreff: Re: [sipcore] WGLC: draft-ietf-sipcore-locparam

Hi all,

The WGLC is being extended to Friday, Sept 13, since many people go on vaca=
tion in August and early September.

Thanks!

Jean



On 8/15/19 2:43 PM, A. Jean Mahoney wrote:
> Hi all,
>=20
> This begins the Working Group Last Call of draft-ietf-sipcore-locparam=20
> (Location Source Parameter for the SIP Geolocation Header Field).
>=20
> Please post any feedback to the sipcore mailing list by Friday, August 30=
.
>=20
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-locparam/
>=20
> Thanks!
>=20
> Jean
>=20
> _______________________________________________
> 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


From nobody Mon Sep 16 21:55:02 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 4C3FB1200E9; Mon, 16 Sep 2019 21:55:00 -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 JrzOrXEofSnH; Mon, 16 Sep 2019 21:54:58 -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 45A001200F6; Mon, 16 Sep 2019 21:54:58 -0700 (PDT)
Received: from Svantevit.local (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 x8H4sqBc013449 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 16 Sep 2019 23:54:54 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1568696095; bh=1oXV3l3uoLV7wWo9mj+GOCXhFIeZobsHyFoBAmJvq9A=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=KMEPHalqFeLU2wpFnIAfde8Z9CX0W6uCAoruXsq3pG/J3NWisVFaY3a9n9bhvGwCp qEUL1sMBUP8dVKNVwexrPPMKNHXI17chRDX2jHyqui6kSkTuBQcGabk5LC7l8AZ9iR Ur54KgigjV0agcN2tcuQ3q4zznTn/wCxH6eJj7Rw=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Cc: draft-ietf-sipcore-digest-scheme@ietf.org, SIPCORE <sipcore@ietf.org>
References: <6c0d98f4-3334-b223-edb9-7fc5970ab028@nostrum.com> <CAGL6epLLHb0baJoKO8sgE5j9Y-g+RAQCkYGRJbV+yGL=59t8jA@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <38f283af-3d14-df41-40cf-3281c98bc8b4@nostrum.com>
Date: Mon, 16 Sep 2019 23:54:46 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAGL6epLLHb0baJoKO8sgE5j9Y-g+RAQCkYGRJbV+yGL=59t8jA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------01729875B5DC2E1C5CB140A9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/YnJovaRsAWDuwcgZhXj0-Jt9okk>
Subject: Re: [sipcore] AD Review: 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: Tue, 17 Sep 2019 04:55:00 -0000

This is a multi-part message in MIME format.
--------------01729875B5DC2E1C5CB140A9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


The last call on this document has concluded, and I see no comments 
other than my own AD review. As soon as a new version of the document is 
in the repository, I'll get it scheduled on the next telechat. Thanks!

/a


On 8/29/19 5:41 PM, Rifaat Shekh-Yusef wrote:
> Thanks Adam!
>
> I will fix these issues in the next version of the draft.
>
> Regards,
>  Rifaat
>
>
>
> On Thu, Aug 29, 2019 at 6:11 PM Adam Roach <adam@nostrum.com 
> <mailto:adam@nostrum.com>> wrote:
>
>     This is my AD review for draft-ietf-sipcore-digest-scheme.
>
>     First of all, I want to thank to everyone who put work into making
>     this happen. It's good to be putting in place a more secure
>     authentication mechanism.
>
>     I find no showstoppers in this version of the document, and will be
>     requesting
>     IETF last call on it shortly. I did find some minor issues,
>     described below,
>     that should be treated the same as any other last call comments.
>
>     /a
>
>     ---------------------------------------------------------------------------
>
>     §1.1:
>
>     Please update to use the boilerplate in RFC 8174.
>
>     ---------------------------------------------------------------------------
>
>     §2.5:
>
>      >  The
>      >  ordering of the header field values from the various proxies
>     is not
>      >  significant.
>
>     The phrasing here is a bit confusing, and can be read as
>     contradicting the
>     sentence it follows. I believe what you mean to say can be
>     conveyed with
>     something more like:
>
>         The ordering of values received from proxies relative to values
>         received from other proxies is not significant.
>
>     ---------------------------------------------------------------------------
>
>     §2.6:
>
>      >  1.  The URI included in the challenge has the following BNF:
>
>     Please cite RFC 5234.
>
>     ---------------------------------------------------------------------------
>
>     §3:
>
>      >  This opens the system to the potential of a downgrade attack
>     by man-
>      >  in-the-middle.
>
>     The phrasing here is a bit awkward. I might suggest rephrasing as:
>     "...a downgrade attack by an on-path attacker."
>
>


--------------01729875B5DC2E1C5CB140A9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <p>The last call on this document has concluded, and I see no
      comments other than my own AD review. As soon as a new version of
      the document is in the repository, I'll get it scheduled on the
      next telechat. Thanks!</p>
    <p>/a<br>
    </p>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 8/29/19 5:41 PM, Rifaat Shekh-Yusef
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGL6epLLHb0baJoKO8sgE5j9Y-g+RAQCkYGRJbV+yGL=59t8jA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>Thanks Adam!</div>
        <div><br>
        </div>
        <div>I will fix these issues in the next version of the draft.</div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div> Rifaat</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Thu, Aug 29, 2019 at 6:11
            PM Adam Roach &lt;<a href="mailto:adam@nostrum.com"
              moz-do-not-send="true">adam@nostrum.com</a>&gt; wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">This is my AD review for
            draft-ietf-sipcore-digest-scheme.<br>
            <br>
            First of all, I want to thank to everyone who put work into
            making<br>
            this happen. It's good to be putting in place a more secure<br>
            authentication mechanism.<br>
            <br>
            I find no showstoppers in this version of the document, and
            will be <br>
            requesting<br>
            IETF last call on it shortly. I did find some minor issues,
            described below,<br>
            that should be treated the same as any other last call
            comments.<br>
            <br>
            /a<br>
            <br>
---------------------------------------------------------------------------<br>
            <br>
            §1.1:<br>
            <br>
            Please update to use the boilerplate in RFC 8174.<br>
            <br>
---------------------------------------------------------------------------<br>
            <br>
            §2.5:<br>
            <br>
             &gt;  The<br>
             &gt;  ordering of the header field values from the various
            proxies is not<br>
             &gt;  significant.<br>
            <br>
            The phrasing here is a bit confusing, and can be read as
            contradicting the<br>
            sentence it follows. I believe what you mean to say can be
            conveyed with<br>
            something more like:<br>
            <br>
                The ordering of values received from proxies relative to
            values<br>
                received from other proxies is not significant.<br>
            <br>
---------------------------------------------------------------------------<br>
            <br>
            §2.6:<br>
            <br>
             &gt;  1.  The URI included in the challenge has the
            following BNF:<br>
            <br>
            Please cite RFC 5234.<br>
            <br>
---------------------------------------------------------------------------<br>
            <br>
            §3:<br>
            <br>
             &gt;  This opens the system to the potential of a downgrade
            attack by man-<br>
             &gt;  in-the-middle.<br>
            <br>
            The phrasing here is a bit awkward. I might suggest
            rephrasing as:<br>
            "...a downgrade attack by an on-path attacker."<br>
            <br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------01729875B5DC2E1C5CB140A9--


From nobody Mon Sep 16 23:50:23 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 95A2712004E; Mon, 16 Sep 2019 23:50:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sipcore-callinfo-spam@ietf.org, Brian Rosen <br@brianrosen.net>, sipcore-chairs@ietf.org, br@brianrosen.net, sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <156870302255.17474.2260736817699792687.idtracker@ietfa.amsl.com>
Date: Mon, 16 Sep 2019 23:50:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ok5KWSLG0EjL7hyqBppByE4khiA>
Subject: [sipcore] Barry Leiba's No Objection on draft-ietf-sipcore-callinfo-spam-04: (with COMMENT)
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, 17 Sep 2019 06:50:23 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-sipcore-callinfo-spam-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have a number of minor comments that I hope you'll consider.

— Section 3 —

   SIP request MAY contain several Call-Info header instances of purpose
   "info", either as a single header with a comma-separated list of
   header values or separate headers, or some combination.

Nit: Correctly used, “either” selects one of two choices, not from among three
or more.  I suggest this:

NEW
   SIP request MAY contain several Call-Info header instances of purpose
   "info", as a single header with a comma-separated list of header
   values or as multiple headers, each with one or more header values.
END

   If the entity
   inserting the header field does not have information it wants to link
   to, it MUST use an empty data URL [RFC2397] as a placeholder, as in
   "data:,".  (The Call-Info header field syntax makes the URI itself
   mandatory.)

Nit: The parenthesized bit struck me as oddly placed; I suggest this:

NEW
   Because the Call-Info header field syntax makes the URI mandatory,
   if the entity inserting the header field does not have information it
   wants to link to, it MUST use an empty data URL (“data:,”) [RFC2397]
   as a placeholder.
END

— Section 4 —

   All of the parameters listed below are optional and may appear in any
   combination and order.  Their ABNF is defined in Section 7.  All
   except the 'type' parameter are optional.

The third sentence contradicts the first (I’m guessing it’s a paste error).  I
suggest this:

NEW
   Call-Info header field parameters are listed below.  Their ABNF is
   defined in Section 7, and they may appear in any combination and
   order.  The ‘type’ parameter is REQUIRED, and all others are OPTIONAL.
END

Or, if I guessed wrong about the ‘type’ parameter, the last sentence would be
“All parameters are OPTIONAL.”

   source  The source parameter identifies the entity, by host name,
      domain or IP address, that inserted the 'confidence', 'origin' and
      'type' parameters.  It uses the "host" ABNF syntax.

Where is the “host” ABNF syntax defined?  Perhaps a citation here would help.

— Section 5 —

   generally based on the caller's telephone number or possibly an
   assertion by a trusted caller, as the content cannot be not known.

What does “as the content cannot be not known” mean?  Can you please rephrase
this?

— Section 8.1 —
The first entry in the table is incorrectly formatted: it has the reference
field first instead of last.

— Section 9 —

   as otherwise spoofed calls would likely be mislabeled and
   thus increase the likelihood that the called party is mislead,

“misled”

   Thus, this information MUST
   only be added calls with an attestation level of "Full Attestation"
   [RFC8588] or for calls where the SIP entity inserting the header
   knows to have correct calling number information, e.g., because the
   call originated within the same PBX or the same carrier and the
   operating entity ensures that caller ID spoofing is highly unlikely
   within their realm of responsibility.

“only be added to calls”
“or to calls”
“knows it has correct calling number information”

Actually, the sentence is too long anyway, so I suggest splitting it.  How
about this?:

NEW
   Thus, this information MUST
   only be added to calls with an attestation level of "Full Attestation"
   [RFC8588] or to calls where the SIP entity inserting the header
   knows it has correct calling number information. An example of how it
   might know that is if the call originated within the same PBX or the
   same carrier, and the operating entity ensures that caller ID spoofing
   is highly unlikely within their realm of responsibility.
END



From nobody Tue Sep 17 01:47:41 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 CF687120104; Tue, 17 Sep 2019 01:47:32 -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.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <156871005276.17550.140629635950067628@ietfa.amsl.com>
Date: Tue, 17 Sep 2019 01:47:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/-Wf0qwkQsFTlkSg9AWVR4arpHM4>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-09.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: Tue, 17 Sep 2019 08:47:33 -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-09.txt
	Pages           : 9
	Date            : 2019-09-17

Abstract:
   This document updates RFC 3261 by updating the Digest Access
   Authentication scheme used by the Session Initiation Protocol (SIP)
   to add support for more secure digest algorithms, e.g.  SHA-256 and
   SHA-512-256, to replace the broken MD5 algorithm, which might be used
   for backward compatibility reasons only.


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-09
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-digest-scheme-09

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


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 Sep 17 01:50:17 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 1BC6C120104; Tue, 17 Sep 2019 01:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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_HELO_NONE=0.001, 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 JkSoZJAQXsj4; Tue, 17 Sep 2019 01:50:13 -0700 (PDT)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 CF85D1200EF; Tue, 17 Sep 2019 01:50:13 -0700 (PDT)
Received: by mail-io1-xd30.google.com with SMTP id f12so5599507iog.12; Tue, 17 Sep 2019 01:50:13 -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=C3FtN4k34HwfgEAP1elEHWBV0O4A+cWhP+XLU4XO5jw=; b=Nxmef8cgXDHKy6N+5GlM6DyU97ffoDSfr0d0pSUo/++87LpHNEKTul8/pYj4cTLfNc N5IR/IRty1txf+xX4ZFg7j1m5IK+qgVhGqL5S3+/JNgk9+rn7ty3B4kbysyBpDZpadfA x44/0rm1kjxEUCdegnIo5sAGUWiz67gr2tKwn/ZWxz0YioBO3LHBEZUzF3gDWu12igZ/ l1HIj9uAyy3hNABHxt9q5kbF6ug0RJekpMOhdi8HrrsV5detgmyTFDgZ+9zRJFnPuCbb IfhsC9i5vNXyayLWHh0LV+hWjRtnG5+gFW4PgKByPenl4vwT5TpRnnq90iWg9XmM1Gei w0Yw==
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=C3FtN4k34HwfgEAP1elEHWBV0O4A+cWhP+XLU4XO5jw=; b=aXZwY/AlRQ4aqrvQ5la5eioXFAx7ttfTzsYoSNJW6FgJRGExdBMZGZFdHFX4sgRajF 0sWVqv8EJIQ/3BS5KQKgLe32JaGtHUxWJEFD6SzZEaDaqpSNSQom8hIu30K1ziKQgyFK KlsPHUQDLQcWDIPQ0KHJxDqsiMWhCFi62ok4Aa5GANJ9Ktmv6fqOwtonH3h9SJJq9xBK TEzQMR0fnsZMjcjS9UJlQyAZHikoYLC0BApFFuqPaIVCqGgEQCkxVK6Xos0rbHJxBhML jok/RzWn/sWJ7/PFCU4ZMl8l1pMBQBCZhlGV928N+xjezy+q5Gx20DYkHt3trm2p12jv C//g==
X-Gm-Message-State: APjAAAVGedgOXlQMvbH90WfIjUyckRf/AICnMKG31OlbcdA5GOtaRckS wqj4jhXJJrrK/WkqZf6UO5BSbmRcj06yRv9uyBeKEoN8
X-Google-Smtp-Source: APXvYqwu2J8eqEbMHUzvp5SjkLtCzd40EavyUwC+9rB9v5BABXuLq5uGSWeMcdXH/q+q7DBWyX8hhjZsrfHfr/dSKGU=
X-Received: by 2002:a02:2302:: with SMTP id u2mr2001706jau.70.1568710213031; Tue, 17 Sep 2019 01:50:13 -0700 (PDT)
MIME-Version: 1.0
References: <6c0d98f4-3334-b223-edb9-7fc5970ab028@nostrum.com> <CAGL6epLLHb0baJoKO8sgE5j9Y-g+RAQCkYGRJbV+yGL=59t8jA@mail.gmail.com> <38f283af-3d14-df41-40cf-3281c98bc8b4@nostrum.com>
In-Reply-To: <38f283af-3d14-df41-40cf-3281c98bc8b4@nostrum.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Tue, 17 Sep 2019 04:50:03 -0400
Message-ID: <CAGL6epKHWQxyv8-jkq_vuo-aTiH+WYWzNMegJts=jChesLGLaA@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: draft-ietf-sipcore-digest-scheme@ietf.org, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000000db7e0592bbcff9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/LflEn6WMO6ff6iXNRUqYmQIsSsw>
Subject: Re: [sipcore] AD Review: 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: Tue, 17 Sep 2019 08:50:16 -0000

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

Thanks Adam,

I have just submitted a new version that addresses your comments.
Please, take a look and let me know if you have any further comments.

Regards,
 Rifaat


On Tue, Sep 17, 2019 at 12:54 AM Adam Roach <adam@nostrum.com> wrote:

>
> The last call on this document has concluded, and I see no comments other
> than my own AD review. As soon as a new version of the document is in the
> repository, I'll get it scheduled on the next telechat. Thanks!
>
> /a
>
> On 8/29/19 5:41 PM, Rifaat Shekh-Yusef wrote:
>
> Thanks Adam!
>
> I will fix these issues in the next version of the draft.
>
> Regards,
>  Rifaat
>
>
>
> On Thu, Aug 29, 2019 at 6:11 PM Adam Roach <adam@nostrum.com> wrote:
>
>> This is my AD review for draft-ietf-sipcore-digest-scheme.
>>
>> First of all, I want to thank to everyone who put work into making
>> this happen. It's good to be putting in place a more secure
>> authentication mechanism.
>>
>> I find no showstoppers in this version of the document, and will be
>> requesting
>> IETF last call on it shortly. I did find some minor issues, described
>> below,
>> that should be treated the same as any other last call comments.
>>
>> /a
>>
>>
>> ------------------------------------------------------------------------=
---
>>
>> =C2=A71.1:
>>
>> Please update to use the boilerplate in RFC 8174.
>>
>>
>> ------------------------------------------------------------------------=
---
>>
>> =C2=A72.5:
>>
>>  >  The
>>  >  ordering of the header field values from the various proxies is not
>>  >  significant.
>>
>> The phrasing here is a bit confusing, and can be read as contradicting t=
he
>> sentence it follows. I believe what you mean to say can be conveyed with
>> something more like:
>>
>>     The ordering of values received from proxies relative to values
>>     received from other proxies is not significant.
>>
>>
>> ------------------------------------------------------------------------=
---
>>
>> =C2=A72.6:
>>
>>  >  1.  The URI included in the challenge has the following BNF:
>>
>> Please cite RFC 5234.
>>
>>
>> ------------------------------------------------------------------------=
---
>>
>> =C2=A73:
>>
>>  >  This opens the system to the potential of a downgrade attack by man-
>>  >  in-the-middle.
>>
>> The phrasing here is a bit awkward. I might suggest rephrasing as:
>> "...a downgrade attack by an on-path attacker."
>>
>>
>>
>

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

<div dir=3D"ltr">Thanks Adam,<div><br></div><div>I have just submitted a ne=
w version that addresses your comments.</div><div>Please, take a look and l=
et me know if you have any further=C2=A0comments.</div><div><br></div><div>=
Regards,</div><div>=C2=A0Rifaat</div><div><br></div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Sep 17, 2019 at=
 12:54 AM Adam Roach &lt;<a href=3D"mailto:adam@nostrum.com">adam@nostrum.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <p><br>
    </p>
    <p>The last call on this document has concluded, and I see no
      comments other than my own AD review. As soon as a new version of
      the document is in the repository, I&#39;ll get it scheduled on the
      next telechat. Thanks!</p>
    <p>/a<br>
    </p>
    <div class=3D"gmail-m_8098044080225483566moz-cite-prefix"><br>
    </div>
    <div class=3D"gmail-m_8098044080225483566moz-cite-prefix">On 8/29/19 5:=
41 PM, Rifaat Shekh-Yusef
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div>Thanks=C2=A0Adam!</div>
        <div><br>
        </div>
        <div>I will fix these issues in the next version of the draft.</div=
>
        <div><br>
        </div>
        <div>Regards,</div>
        <div>=C2=A0Rifaat</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"ltr" class=3D"gmail_attr">On Thu, Aug 29, 2019 at 6:1=
1
            PM Adam Roach &lt;<a href=3D"mailto:adam@nostrum.com" target=3D=
"_blank">adam@nostrum.com</a>&gt; wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This is my AD r=
eview for
            draft-ietf-sipcore-digest-scheme.<br>
            <br>
            First of all, I want to thank to everyone who put work into
            making<br>
            this happen. It&#39;s good to be putting in place a more secure=
<br>
            authentication mechanism.<br>
            <br>
            I find no showstoppers in this version of the document, and
            will be <br>
            requesting<br>
            IETF last call on it shortly. I did find some minor issues,
            described below,<br>
            that should be treated the same as any other last call
            comments.<br>
            <br>
            /a<br>
            <br>
---------------------------------------------------------------------------=
<br>
            <br>
            =C2=A71.1:<br>
            <br>
            Please update to use the boilerplate in RFC 8174.<br>
            <br>
---------------------------------------------------------------------------=
<br>
            <br>
            =C2=A72.5:<br>
            <br>
            =C2=A0&gt;=C2=A0 The<br>
            =C2=A0&gt;=C2=A0 ordering of the header field values from the v=
arious
            proxies is not<br>
            =C2=A0&gt;=C2=A0 significant.<br>
            <br>
            The phrasing here is a bit confusing, and can be read as
            contradicting the<br>
            sentence it follows. I believe what you mean to say can be
            conveyed with<br>
            something more like:<br>
            <br>
            =C2=A0=C2=A0=C2=A0 The ordering of values received from proxies=
 relative to
            values<br>
            =C2=A0=C2=A0=C2=A0 received from other proxies is not significa=
nt.<br>
            <br>
---------------------------------------------------------------------------=
<br>
            <br>
            =C2=A72.6:<br>
            <br>
            =C2=A0&gt;=C2=A0 1.=C2=A0 The URI included in the challenge has=
 the
            following BNF:<br>
            <br>
            Please cite RFC 5234.<br>
            <br>
---------------------------------------------------------------------------=
<br>
            <br>
            =C2=A73:<br>
            <br>
            =C2=A0&gt;=C2=A0 This opens the system to the potential of a do=
wngrade
            attack by man-<br>
            =C2=A0&gt;=C2=A0 in-the-middle.<br>
            <br>
            The phrasing here is a bit awkward. I might suggest
            rephrasing as:<br>
            &quot;...a downgrade attack by an on-path attacker.&quot;<br>
            <br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </div>

</blockquote></div>

--00000000000000db7e0592bbcff9--


From nobody Thu Sep 19 03:57:00 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 B637A120033; Thu, 19 Sep 2019 03:56:59 -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.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <156889061963.4523.8682530466822522896@ietfa.amsl.com>
Date: Thu, 19 Sep 2019 03:56:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/puCCgbSciTHRyCuLi9jRcfnxL3Y>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-digest-scheme-10.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, 19 Sep 2019 10:57:00 -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-10.txt
	Pages           : 9
	Date            : 2019-09-19

Abstract:
   This document updates RFC 3261 by updating the Digest Access
   Authentication scheme used by the Session Initiation Protocol (SIP)
   to add support for more secure digest algorithms, e.g.  SHA-256 and
   SHA-512-256, to replace the broken MD5 algorithm, which might be used
   for backward compatibility reasons only.


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-10
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-digest-scheme-10

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


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 Sep 22 06:27:17 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 E62E9120018; Sun, 22 Sep 2019 06:27:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sipcore-callinfo-spam@ietf.org, Brian Rosen <br@brianrosen.net>, sipcore-chairs@ietf.org, br@brianrosen.net, sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <156915883085.1440.10366490853113567918.idtracker@ietfa.amsl.com>
Date: Sun, 22 Sep 2019 06:27:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/_J7vmS49zKqSYhpYqj9fZpnMdZc>
Subject: [sipcore] Alexey Melnikov's No Objection on draft-ietf-sipcore-callinfo-spam-04: (with COMMENT)
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, 22 Sep 2019 13:27:11 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-sipcore-callinfo-spam-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for this document.

I agree with Barry’s comments. One extra nit from myself:

In 8.1.  SIP Call-Info Header Field Parameters:

The order of fields in the first registration is rotated by one field. I don’t
think this was intended.



From nobody Mon Sep 30 03:14:55 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 8D20A120071; Mon, 30 Sep 2019 03:14:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sipcore-callinfo-spam@ietf.org, Brian Rosen <br@brianrosen.net>, sipcore-chairs@ietf.org, br@brianrosen.net, sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <156983848749.460.11029361799621342593.idtracker@ietfa.amsl.com>
Date: Mon, 30 Sep 2019 03:14:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/_rQnUqHDLQDl672SWG26XseVesI>
Subject: [sipcore] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-sipcore-callinfo-spam-04=3A_=28with_COMMENT=29?=
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, 30 Sep 2019 10:14:48 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-sipcore-callinfo-spam-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document. Please find a couple of COMMENTs
and NITs below.

Regards,

-éric

== COMMENTS ==

-- Section 1 --
C.1) I suggest to remove or explain "blue pages" as it probably a USA thing (I
have no clue what are those pages being based in Belgium).

-- Section 4 --
C.2) the word "probability" is used with a range of 0 to 100. This is somehow
confusing as the word "probability" has a mathematical definition which is not
applicable here, "confidence" or "certainty' could be a better wording.

C.3) using an IP address as the source may not be very useful for most
applications/users/consumers of this header. Why not having a FQDN as a MUST?

-- Section 5 --
C.4) In the first paragraph, I cannot figure out how to both have "Other
strings may be used" and "Additional labels are registered with IANA." in the
same paragraph.

-- Section 6.2 --
C.5) is there a reason why "http" is used rather than "https" ?

== NITS ==

-- Section 5 --
N.1) in the enumeration of labels, adding a ":" after the label would improve
the readability.

-- Section 8.1 --
The table is misaligned.


