Re: [sipcore] Benjamin Kaduk's No Objection on draft-ietf-sipcore-originating-cdiv-parameter-07: (with COMMENT)

That is fine for me.  To be clear, I had no objection to the original, and
I was just confused.  The follow-up discussion helped me, and I am not
requesting a chamge to the document for my sake.

-Benjamin

On Sun, Dec 09, 2018 at 11:07:36PM +0000, marianne.mohali@orange.com wrote:
> Hi Benjamin,
> 
> We had email exchanges about the syntax and how to make it aligned with what has been designed (and is already implemented by networks).
> Paul is correct existing syntax 1) is equivalent to 1a) by following ABNF rules.
> The idea is to optimize the syntax so 1) should be the correct form.
>  
> Are you fine with that?
> 
> BR,
> Marianne
> 
> -----Message d'origine-----
> De : sipcore [mailto:sipcore-bounces@ietf.org] De la part de Paul Kyzivat
> Envoyé : jeudi 6 décembre 2018 17:37
> À : Benjamin Kaduk
> Cc : sipcore@ietf.org
> Objet : Re: [sipcore] Benjamin Kaduk's No Objection on draft-ietf-sipcore-originating-cdiv-parameter-07: (with COMMENT)
> 
> On 12/6/18 4:23 AM, Benjamin Kaduk wrote:
> 
> >     sessioncase-param        = "sescase" EQUAL ("orig"/"term")/ orig-cdiv
> > 
> > It's quite possible I'm just confused about the ABNF, but why do we need the
> > grouping?
> 
> IIUC, you are asking if the above:
> 
> 1) sessioncase-param  = "sescase" EQUAL ("orig"/"term")/ orig-cdiv
> 
> is equivalent to:
> 
> 2) sessioncase-param  = "sescase" EQUAL "orig"/"term"/ orig-cdiv
> 
> The answer is no, it isn't. Using more bracketing to show the syntax 
> more clearly, (1) is equivalent to:
> 
> 1a) sessioncase-param  = ("sescase" EQUAL ("orig"/"term")) / orig-cdiv
> 
> while (2) is equivalent to:
> 
> 2a) sessioncase-param  = ("sescase" EQUAL "orig") / "term" / orig-cdiv
> 
> 	Thanks,
> 	Paul
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 
> _________________________________________________________________________________________________________________________
> 
> 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.
> 