Re: [sipcore] Benjamin Kaduk's Discuss on draft-ietf-sipcore-reason-q850-loc-06: (with DISCUSS and COMMENT)

<R.Jesske@telekom.de> Mon, 11 March 2019 08:21 UTC

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 6F14B13103D; Mon, 11 Mar 2019 01:21:44 -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, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ZO0U5c8LkO-s; Mon, 11 Mar 2019 01:21:42 -0700 (PDT)
Received: from mailout21.telekom.de (MAILOUT21.telekom.de [194.25.225.215]) (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 95B1F130F4C; Mon, 11 Mar 2019 01:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1552292502; x=1583828502; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=l3/d+jACLV0CEOUppferx/5lqrYoCVx6EUJ3KrWl8gM=; b=J1L5d38Xudm4hKuStmDbQ8Y2/hgDP1YvZ9wKehLS9USMoNqN7NZf/5E4 Th/eHHNw5+fUwBAdDvQqkL+5kUNB0vZaSBqqTygNwtUK2bOh0WdF8USw3 j5z8LZLsIRlS5Fz4GGIqJsHT6lJ3qcUhwW5tOrglbg8uTMZW8QEhkvN9v +1VyKAi7Z+hs66nDXxO6osyCtodZ/QTCoLFfOgm/h65+Wn9Y/ziSSb0Sx dUMOp2MFknqNhbt06BG2SywtToOy9UtYFdxyTlKvo/hMOGU01tzeiVXng 9geyYy0fG7WyST/IsxQBLeZppvNV15WLYClsmSskhoybnNzl4GFpYyQxJ A==;
Received: from qde8e4.de.t-internal.com ([10.171.255.33]) by MAILOUT21.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Mar 2019 09:21:39 +0100
X-IronPort-AV: E=Sophos;i="5.58,467,1544482800"; d="scan'208";a="484665874"
Received: from he105651.emea1.cds.t-internal.com ([10.169.119.62]) by QDE8PP.de.t-internal.com with ESMTP/TLS/AES256-SHA; 11 Mar 2019 09:20:36 +0100
Received: from HE105651.EMEA1.cds.t-internal.com (10.169.119.62) by HE105651.emea1.cds.t-internal.com (10.169.119.62) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 11 Mar 2019 09:20:35 +0100
Received: from HE104163.emea1.cds.t-internal.com (10.171.40.38) by HE105651.EMEA1.cds.t-internal.com (10.169.119.62) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 11 Mar 2019 09:20:35 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.15) by O365mail05.telekom.de (172.30.0.230) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 11 Mar 2019 09:20:35 +0100
Received: from FRXPR01MB0135.DEUPRD01.PROD.OUTLOOK.DE (10.158.150.149) by FRXPR01MB0133.DEUPRD01.PROD.OUTLOOK.DE (10.158.150.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.20; Mon, 11 Mar 2019 08:20:35 +0000
Received: from FRXPR01MB0135.DEUPRD01.PROD.OUTLOOK.DE ([fe80::1dd6:9036:77f4:3bdb]) by FRXPR01MB0135.DEUPRD01.PROD.OUTLOOK.DE ([fe80::1dd6:9036:77f4:3bdb%6]) with mapi id 15.20.1686.021; Mon, 11 Mar 2019 08:20:35 +0000
From: R.Jesske@telekom.de
To: noreply@ietf.org, iesg@ietf.org
CC: draft-ietf-sipcore-reason-q850-loc@ietf.org, sipcore-chairs@ietf.org, sipcore@ietf.org
Thread-Topic: [sipcore] Benjamin Kaduk's Discuss on draft-ietf-sipcore-reason-q850-loc-06: (with DISCUSS and COMMENT)
Thread-Index: AQHU1MtbypIRSkP9z0SB907dYCfr7qYGG/mQ
Date: Mon, 11 Mar 2019 08:20:34 +0000
Message-ID: <FRXPR01MB01350BEB15B22E9E5FFB936AF9480@FRXPR01MB0135.DEUPRD01.PROD.OUTLOOK.DE>
References: <155193609023.13714.4531517779875308584.idtracker@ietfa.amsl.com>
In-Reply-To: <155193609023.13714.4531517779875308584.idtracker@ietfa.amsl.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.220]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 88640678-f56b-4115-e0f1-08d6a5fa6f88
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:FRXPR01MB0133;
x-ms-traffictypediagnostic: FRXPR01MB0133:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <FRXPR01MB01337EEEE9E0F1CA9CE4BC1BF9480@FRXPR01MB0133.DEUPRD01.PROD.OUTLOOK.DE>
x-forefront-prvs: 09730BD177
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(346002)(39860400002)(376002)(366004)(189003)(199004)(55016002)(53936002)(71190400001)(71200400001)(9686003)(14454004)(26005)(186003)(561944003)(33656002)(74482002)(76176011)(97736004)(7696005)(6306002)(52396003)(105586002)(106356001)(6116002)(3846002)(86362001)(5660300002)(81166006)(256004)(81156014)(8676002)(2906002)(14444005)(450100002)(305945005)(75402003)(7736002)(102836004)(68736007)(478600001)(110136005)(486006)(966005)(54906003)(476003)(446003)(11346002)(72206003)(316002)(4326008)(66574012)(66066001)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:FRXPR01MB0133; H:FRXPR01MB0135.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-microsoft-exchange-diagnostics: 1; FRXPR01MB0133; 23:NTFTdVE1QLuz1oAG9b8pAZyrmfcM8BRyoUQeKFghRyRmI6TQOgczTAteuUVgGEcQ/oXNyCZJz0cVeK+bd9sjtNWbiYfoswW+vIQVFuQ0dkKKqQVAMZzF6A5cixLNTrVMmDNiitLPh+L6qQyQ2CFpeKSPARWy3JNkWW01EhTfQnHBCazmymEmZQylRcHWc1prTyFXWQ4YFz3U0NPDBTstPd9L6j8j76WcdHOafBwmhKvtPIaZ7F/4eQc5jf4ltmyJo2HRrrhe7FMDoe9Ugi0YhyOBsvjZ31+Pci5hWpqXLurS/jTLHayyc2Okg/omDhE8Izi7yw6efFVOWN88ZRoZQIzfKm5VScYDg8uHECRB/5zdDDCArMAT2cZW4QG8Jb4oc9bV5wpXbt7gW/okgvrzx3A+Ge7+Yfy8mZc4OOUlPqkYFhL56GiiXQRiM/p5k/xTn+Wv4RMmkNauo0bo9O+3wXtHTLjncvymmCdXVsbuR/bukXWxpyJkP6tSpzS3GuE9sfrPP0l4v3hSRyKWeEq1U4CUTmTjXL7qo65oO6qdykkUC3sjjYgQmIjCjbjw0uQMTNhkeywiLHRrdreF3v7kft5mdT9o6azeGGw7EKH7mjZBbaP1TDlUAOMg4GZfNLpErnxoJd/N7KUNoabfBWmLFCGQpX/a37aKPOJkY5wuZfRvsKwjqgvmZiVQWEKmetGde9dTFhPj7QQS4yGEIhWdi2Aigwmk1wRdN+GabnbnLbNDgp5pvIVJJX7lkAvKiAiLWAvJNWC7U8iLtbKZ0XKtyG2ijg9GvwI/iue+5cqGsFGiNVeMi38s7K65qYgQ7ik6T2UX+p5xHsQ+YdW0mr7Io+ihUc2JFZ+eCqVsNzOqqX3WH2ji5ParcVMvrpr5xAyaW++V+UgmPMwlUfpcP6Sdg5xb08QbqXgQYqrg/anNB8iKb8UEHw4R/9DbE7jEaa1Q0p6xlUG1qDE/d5aIOYdp3B+RnQG1gO17H5IDWUSNgyZ0pzXbByF1WavHgCzzzgqrNDtowFmOEQ7ned6RwJHN2WdU0h3SXdozvREIXBhSWgcmcwSFRSZuRT1voczgRmyR2hHiUb4Z3bV9pnNrDN5sUip97bUvMNUMYX72BLM2e1MxF42Nz8ZDAcKj26YsbDvXws6XtjlOTXqiB4rU2O+imV0+fHTWlZk0FKC8vpaMnIPvGTGE836rLfW6zfGuytz80sy2MbB8MzmTCR7iPsN29mDwexc+RnKgfOuXc1cD9sj1PsKbKgpbjbeE1zWUr7pw
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 0sb+HTJLiF6F5+DvtqkZvnNVVL5+LTvBl/lY7+XVr1h7Hc52w4DD/m2C4jpNPFM6OjeAbahkg0vjlqF3WTbVemr9lNhUIDpv+ghfiy1qugi3hXKR+98IfeVhP3Lyfmqdah7Sbt/it9Qjj4in8xHVmEyanugxQt4N1hU3Po8bqXfM4wVavJek+icH8HCQORthAEcz2PqB91LWLR10ix/7PnLKgBSIV0gZ5bz9DbgMP4zqdXqqMxS7abVHm2pcjJOEsWlrfY5LSpbJSNEqPSKIVG0zqa5U5Gd4ccvKN/M9+kYRWu/Wivg1fGa6JaZ+uicHfrnK/ZZztIdOQayXm018IJ1ingpgEUYSuThxUDzh5RfymD4BnVGNiyxmrwFV2OVxxjF487YAniCPbBmL3kikhpoSx8Kfp0Bi86ZbByJHTQ8=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 88640678-f56b-4115-e0f1-08d6a5fa6f88
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2019 08:20:34.9961 (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-Transport-CrossTenantHeadersStamped: FRXPR01MB0133
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/HyV0wfEiFj_qzx3r2NsM7SfWAXo>
Subject: Re: [sipcore] Benjamin Kaduk's Discuss on draft-ietf-sipcore-reason-q850-loc-06: (with DISCUSS and COMMENT)
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, 11 Mar 2019 08:21:45 -0000

Hi,
Thank you for your comments. I went through the comments and 
here are my answers and proposals to the comments made.
Sorry If some of you get the mail twice, since I answered in another way already.


Discuss on Section 4
Do you want to see something beyond the Note I put in?
Note: These are the values defined  within <xref target="Q.850"/> as location. Thus other values are not within the scope of this document.

The last try to change these values in ITU-T was around 2001/2002 for some mobile network code points. This was rejected since operators said that there is willingness to change ISUP for such coding points. The values are stable since 20 years so there will be no change of these values in future, since invest will go into IP based networks like IMS. 

Comments on Section 1,3 and 4
Nits on Section 1+3 corrected.

Section 4:
I try to reformulate the sentence.
Proposal:

   UAC  or UAS SHALL include the location parameter in a request or response   when setting up the Reason header field with a [Q.850] cause.  This approach is only  possible in cases when the ISUP [Q.850] location is available.

If you are OK with these changes I will produce a new draft and upload it.

Thank you and Best Regards

Roland
> -----Ursprüngliche Nachricht-----
> Von: sipcore <sipcore-bounces@ietf.org> Im Auftrag von Datatracker on
> behalf of Benjamin Kaduk
> Gesendet: Donnerstag, 7. März 2019 06:22
> An: The IESG <iesg@ietf.org>
> Cc: draft-ietf-sipcore-reason-q850-loc@ietf.org; sipcore-chairs@ietf.org;
> sipcore@ietf.org
> Betreff: [sipcore] Benjamin Kaduk's Discuss on draft-ietf-sipcore-reason-
> q850-loc-06: (with DISCUSS and COMMENT)
> 
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-sipcore-reason-q850-loc-06: Discuss
> 
> 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-reason-q850-loc/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I support Adam's Discuss.
> 
> I also think that the Section 4 text:
> 
>    The use of the location parameter is restricted to Q850 cause values.
>    Other values MUST be ignored if present.
> 
> needs to be clear about whether it is intended to limit to the exact 16 strings
> listed above, or whether the intent is to update with Q850 if new values are
> allocated.  Are string aliases allowed for the "national-use" codepoints if
> allocated within a given nation?
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 1
> 
>    the reason of release.  The reason of release does indicate why a SIP
>    Dialog or an PSTN call, in case where the call was interworked to the
> 
> nits: s/does indicate/indicates/ ; s/an PSTN/a PSTN/
> 
> Section 3
> 
>    The primary intent of the parameter defined in this specification is
>    for use in IMS (IP Multimedia Subsystem) networks defined by 3GPP but
>    also open to be used by any other network that includes ISUP
> 
> nit: s/also/it is also/
> 
> Section 4
> 
>    Depending on whether the message is a request or a response the UAC
>    or UAS SHALL include the location parameter when setting up the
>    Reason header field with a [Q.850] cause.  This approach is only
>    possible in cases when the ISUP [Q.850] location is available.
> 
> I don't understand what depends on whether the message is a request or a
> response.
> 
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore