Subject: Re: [dispatch] draft-jesske-dispatch-reason-loc-q850-00

From: "Belling, Thomas (Nokia - DE/Munich)" <[email-masked]>
Date: Fri, 3 Mar 2017 11:14:11 +0000

Dear Roland

I understand that the motivation of the work is to provide interworking for the ISUP Cause location parameter, and the suggested values in the draft also provide a 1-to-1 mapping. This is fine for me as there are use cases where not only the ISUP cause itself, but also the location could be of interest, e.g. to distinguish between Network Determined User Busy and Used Determined User Busy (NDUB/UDUB). It also feels natural to extent the SIP reason header for that purpose which was originally designed to transport ISUP cause values (although it also has other usages, and the wording in the scope of the draft could be updated a bit accordingly)

To avoid confusion about the semantics and purpose of the new parameter, I would suggest to clarify this in the following manner:

-          Change the title of the draft to "ISUP Cause Location Parameter for the SIP Reason Header Field"

-          Call the parameter "isup-cause-location"

-          Improve the wording in the scope a bit to clarify that the reason header can also be used to transport other Reasons than ISUP causes, but the new parameter is only applicable in combination with ISUP causes.

Thomas

----------------------------------
Dr. Thomas Belling
3GPP Standardisation
NOKIA Networks

Nokia Solutions and Networks Management International GmbH
Geschäftsleitung / Board of Directors: Andreas Sauer, Stephanie Werner
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRB 198081

From: dispatch [mailto:[email-masked]] On Behalf Of Dawes, Peter, Vodafone Group
Sent: Tuesday, February 28, 2017 4:18 PM
To: DOLLY, MARTIN C <[email-masked]>; [email-masked]
Cc: [email-masked]
Subject: Re: [dispatch] draft-jesske-dispatch-reason-loc-q850-00

you are right Marianne, my mistake

Rgds,
Peter

From: dispatch [mailto:[email-masked]] On Behalf Of DOLLY, MARTIN C
Sent: 28 February 2017 15:11
To: [email-masked]<mailto:[email-masked]>
Cc: [email-masked]<mailto:[email-masked]>
Subject: Re: [dispatch] draft-jesske-dispatch-reason-loc-q850-00

I support as well
Martin C. Dolly
Lead Member of Technical Staff
Core & Government/Regulatory Standards
AT&T
Cell: +1.609.903.3360<tel:+1.609.903.3360>
Email: [email-masked]<mailto:[email-masked]>

On Feb 28, 2017, at 9:04 AM, "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>> wrote:
Hi All,

I support this Internet-Draft to progress in IETF.

I suggest to have some text to refer to RFC 6432 to ease the knowledge of the background and the usage of the Reason header field in error responses. I can help to provide some text.

On Peter's comment, I think it is correct to have "location=LN" in the example as the new parameter syntax is               resp-location    =  "location" EQUAL string

Best Regards,
Marianne

De : dispatch [mailto:[email-masked]] De la part de Dawes, Peter, Vodafone Group
Envoyé : mardi 21 février 2017 13:11
À : [email-masked]<mailto:[email-masked]>
Objet : [dispatch] draft-jesske-dispatch-reason-loc-q850-00

Hi All,
I have read through draft-jesske-dispatch-reason-loc-q850-00 and I think it is clearly written and useful. One comment, I think the example in clause 5 should say "resp-location=LN" instead of "location=LN".

Regards,
Peter

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
_______________________________________________
dispatch mailing list
[email-masked]<mailto:[email-masked]>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_dispatch&d=DQICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=9y5R3pOq5Oz0unZ73c_Z6ifowd5txi2vvpvlY7MtzoY&s=JGQJ2uxeZGcN3WdhemtyHXnm2Iy-OSng_l27WUYpOlI&e=