Re: [3gpp-ietf-coord] Re : QCI to Diffserv mapping

[Magnus Westerlund <[e-mail]>]

Hi,

I have sent a request. 

Cheers

Magnus Westerlund

> -----Original Message-----
> From: Gonzalo Camarillo <[e-mail]>
> Sent: den 18 juli 2019 11:35
> To: [e-mail]; Magnus Westerlund
> <[e-mail]>
> Cc: DOLLY, MARTIN C <[e-mail]>; [e-mail]; tsvwg-
> [e-mail]; [e-mail]; [e-mail]
> Subject: Re: Re : [3gpp-ietf-coord] QCI to Diffserv mapping
> 
> Lionel, Magnus,
> 
> I do not think I have seen any follow up on this.
> 
> Lionel, please confirm whether you have a draft agenda for the meeting on
> Monday (beyond this topic).
> 
> Magnus, per my email below, could you please secure a room for us for
> Monday lunch?
> 
> Cheers,
> 
> Gonzalo
> 
> On 04-Jul-19 10:14, Gonzalo Camarillo wrote:
> > Thanks, Lionel!
> >
> > Magnus, with the information below, do you need anything else at this
> point?
> >
> > Regarding the coordination meeting in Montreal, Magnus can probably
> > get us a room with a conference bridge (or we can use a laptop, as I
> > think we did last time). Our traditional slot for that is Monday lunch.
> >
> > By the way, do you have a draft agenda for the coordination meeting,
> > in addition to this topic?
> >
> > Cheers,
> >
> > Gonzalo
> >
> > On 04-Jul-19 01:40, [e-mail] wrote:
> >> Hi Gonzalo, Martin,
> >>
> >> We have discussed this point with Georg. According to the purpose of
> >> the draft and early reaction of 3GPP folks, it appears that there is
> >> currently no requirement for such mapping done in IETF.
> >>
> >> The QCI/DSCP mapping is only for information, as the final mapping
> >> will be nyvow decided by network operators, based on the QCI values
> >> but also on other criteria defined by the operators.
> >>
> >> Moreover, if you look at the 3GPP TS 23.203 specification across
> >> releases, you will see that the new QCI values are continuously
> >> defined by 3GPP depending on new use cases. For instance, there is an
> >> ongoing didcussion to create additional values. So having a document
> >> defining the mapping at the IETF side would seem not relevant as the
> >> RFC, even if informational, could be already obsolete when published.
> >>
> >> There might be a need to have an update version of the mapping but,
> >> if deemed required, interested parties should bring such a material
> >> in 3GPP, to allow maintaining up to date the document.
> >>
> >> According that there is no specific requirement from 3GPP and an IETF
> >> RFC, even information would be quite useless, 3GPP would be reluctant
> >> to see any recommendation on the QCI/DSCP mapping provided in a IETF
> >> document that would not be under the 3GPP control.
> >>
> >> Now, from an IETF point of view, if there is a strong push for such a
> >> document, except the natural push from the authors, it would be up to
> >> IETF to decide what to do in this area. If it is decided to move
> >> forward, it should be made clear in the document that the proposed
> >> mapping is only for information, not a recommendation, given as
> example.
> >> It should also be highlighted that the QCI values listed in the
> >> document may not be up to date.
> >>
> >> I hope that the feedback is clear.
> >> Anyhow, it will be useful to discuss this point in our coordination
> >> meeting. Unfortunately, I will not be in Montreal but, if we could
> >> set up an audio bridge as last time, it would be great.
> >>
> >> Regards,
> >>
> >> Lionel
> >>
> >>
> >> -------- Message original --------
> >> Objet : Re: [3gpp-ietf-coord] QCI to Diffserv mapping De : "DOLLY,
> >> MARTIN C"
> >> À : Gonzalo Camarillo
> >> Cc : MORAND Lionel TGI/OLN ,Magnus Westerlund
> >> ,[e-mail],[e-mail],vshaikh@perspectalabs
> >> .com,[e-mail]
> >>
> >>         Greetings
> >>
> >>         The NS/EP service in the USA has major issues w this draft that
> >>         is against efforts we standardized in 3GPP and ATIS
> >>
> >>         We commented on the list and communicated w author, little
> >> changes
> >>
> >>         If this became a 3GPP dependency, we and the others would have
> >>         sustained objections
> >>
> >>         Thanks
> >>
> >>         Martin C. Dolly
> >>
> >>         Lead Member of Technical Staff
> >>
> >>         Government & Services Standards
> >>
> >>         AT&T
> >>
> >>         Cell: +1.609.903.3360
> >>
> >>         Email: [e-mail] <mailto:[e-mail]>
> >>
> >>
> >>         On Jul 3, 2019, at 2:51 PM, Gonzalo Camarillo
> >>         <[e-mail]
> >>         <mailto:[e-mail]>> wrote:
> >>
> >>             Hi Lionel,
> >>
> >>             did you reach any conclusion? In particular, I would like to
> >>             understand
> >>             whether we need to organize the traditional 3GPP-IETF
> >>             coordination
> >>             meeting on the Monday of the upcoming IETF meeting in
> >>             Montreal to
> >>             discuss this or other issues.
> >>
> >>             Thanks,
> >>
> >>             Gonzalo
> >>
> >>             On 02-Jul-19 13:11, Gonzalo Camarillo wrote:
> >>
> >>                 Hi Lionel,
> >>
> >>
> >>                 yes, exactly; knowing 3GPP's position on this would be
> >>                 very helpful in
> >>
> >>                 order to decide on next steps. Please, let us know after
> >>                 you touch base
> >>
> >>                 with Georg later today. Thanks.
> >>
> >>
> >>                 Cheers,
> >>
> >>
> >>                 Gonzalo
> >>
> >>
> >>                 On 02-Jul-19 11:58, [e-mail]
> >>                 <mailto:[e-mail]> wrote:
> >>
> >>                     Hi Gonzalo,
> >>
> >>
> >>                     We will discuss this point with Georg today during
> >>                     an 3GPP internal coordination meeting.
> >>
> >>                     On the tsvwg mailing list, I think that the
> >>                     conclusion was to set up a discussion at the next
> >>                     IETF meeting to see what could be done in this area.
> >>
> >>                     Honestly, I'm not sure that such a work would be
> >>                     useful if not supported by 3GPP. So if anything is
> >>                     finally done, it could only be for information.
> >>
> >>
> >>                     Coming back to you later.
> >>
> >>
> >>                     Regards,
> >>
> >>
> >>                     Lionel
> >>
> >>
> >>                         -----Message d'origine-----
> >>
> >>                         De : Gonzalo Camarillo
> >>                         [mailto:[e-mail]]
> >>
> >>                         Envoyé : vendredi 28 juin 2019 16:09
> >>
> >>                         À : MORAND Lionel TGI/OLN; Magnus Westerlund;
> >>                         [e-mail]
> >>                         <mailto:[e-mail]>
> >>
> >>                         Cc : [e-mail]
> >>                         <mailto:[e-mail]>
> >>
> >>                         Objet : Re: [3gpp-ietf-coord] QCI to Diffserv
> >>                         mapping
> >>
> >>
> >>                         Hi Lionel,
> >>
> >>
> >>                         I have not seen any follow up on this issue
> >>                         during this month (see
> >>
> >>                         below). What is the current status? Thanks.
> >>
> >>
> >>                         Cheers,
> >>
> >>
> >>                         Gonzalo
> >>
> >>
> >>                         On 29-May-19 12:37, [e-mail]
> >>                         <mailto:[e-mail]> wrote:
> >>
> >>                             Thank you!
> >>
> >>
> >>                             I have seen the ongoing discussion on this
> >>                             topic.
> >>
> >>                             I will send soon an email clarifying the
> >>                             current 3GPP position on this topic.
> >>
> >>                             It is important that any work on the QCI
> >>                             mapping is aligned with real 3GPP
> >>
> >>                         requirements.
> >>
> >>
> >>                             Regards,
> >>
> >>
> >>                             Lionel
> >>
> >>
> >>                                 -----Message d'origine-----
> >>
> >>                                 De : 3gpp-ietf-coord
> >>                                 [mailto:[e-mail]] De
> >>                                 la
> >>
> >>                         part
> >>
> >>                                 de Magnus Westerlund
> >>
> >>                                 Envoyé : mercredi 29 mai 2019 11:09
> >>
> >>                                 À : [e-mail]
> >>                                 <mailto:[e-mail]>
> >>
> >>                                 Cc : [e-mail]
> >>                                 <mailto:[e-mail]>
> >>
> >>                                 Objet : [3gpp-ietf-coord] QCI to
> >>                                 Diffserv mapping
> >>
> >>
> >>                                 Hi,
> >>
> >>
> >>                                 A topic that may require coordination
> >>                                 between 3GPP and IETF is this
> >>
> >>                                 individual proposal
> >>
> >>
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf
> >> .org_doc_draft-2Dhenry-2Dtsvwg-2Ddiffserv-2Dto-
> 2Dqci_&d=DwIGaQ&c=LFYZ
> >> -o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkT
> >>
> AVPAgFzc3jf6cvGf6x0g&s=XunaN7YxIvVUKNlYB0LFqWpZkcOVXTV8rK7BUaJl
> vyo&e=
> >>
> >>
> >>                                 It has been presented once in TSVWG
> >>                                 before, when questions where
> >>
> >>                         raised
> >>
> >>                                 about the relation to 3GPP. I haven't
> >>                                 seen any good answer to this
> >>
> >>                                 question. Also the authors have updated
> >>                                 the draft and that has resulted
> >>
> >>                                 in some additional discussion in this
> >>                                 thread:
> >>
> >>
> >>
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf
> >> .org_arch_msg_tsvwg_r3jAeNPcz83K0nFyQD4yObJkC-
> 2D&d=DwIGaQ&c=LFYZ-o9_H
> >> UMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkTAVPAg
> >> Fzc3jf6cvGf6x0g&s=fzf5xDu0zA-11_7wZOZws5A-
> XtDJHPg8MX6T3brLff4&e=
> >>
> >>                                 A
> >>
> >>
> >>                                 So far no decision has been made if this
> >>                                 should be adopted or not, but I
> >>
> >>                                 would not be surprised if the TSVWG
> >>                                 Chairs and I (as TSV AD) do get the
> >>
> >>                                 question about adoption.
> >>
> >>
> >>                                 Input from a 3GPP perspective would be
> >>                                 appreciated on this document.
> >>
> >>
> >>                                 Cheers
> >>
> >>
> >>                                 Magnus Westerlund
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> -
> >>
> >>                                 Network Architecture & Protocols,
> >>                                 Ericsson Research
> >>
> >>
> >> ---------------------------------------------------------------------
> >> -
> >>
> >>                                 Ericsson AB                 | Phone  +46
> >>                                 10 7148287
> >>
> >>                                 Torshamnsgatan 23           | Mobile +46
> >>                                 73 0949079
> >>
> >>                                 SE-164 80 Stockholm, Sweden | mailto:
> >>
> >>                         [e-mail]
> >>                         <mailto:[e-mail]>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> -
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >>
> >>                                 3gpp-ietf-coord mailing list
> >>
> >>                                 [e-mail]
> >>                                 <mailto:[e-mail]>
> >>
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mai
> >> lman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r
> >> =G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g
> >> &s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=
> >>
> >>
> >>
> >>
> >>
> __________________________________________________________
> ____
> >>
> >>
> >>
> __________________________________________________________
> _
> >>
> >>
> >>                             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.
> >>
> >>
> >>
> >> _______________________________________________
> >>
> >>                             3gpp-ietf-coord mailing list
> >>
> >>                             [e-mail]
> >>                             <mailto:[e-mail]>
> >>
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mai
> >> lman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r
> >> =G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g
> >> &s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=
> >>
> >>
> >>
> >>
> >>
> __________________________________________________________
> ___________
> >> ____________________________________________________
> >>
> >>
> >>                     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.
> >>
> >>
> >>
> >>                 _______________________________________________
> >>
> >>                 3gpp-ietf-coord mailing list
> >>
> >>                 [e-mail]
> >> <mailto:[e-mail]>
> >>
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mai
> >> lman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r
> >> =G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g
> >> &s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=
> >>
> >>
> >>
> >>             _______________________________________________
> >>             3gpp-ietf-coord mailing list
> >>             [e-mail] <mailto:[e-mail]>
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mai
> >> lman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r
> >> =G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g
> >> &s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=
> >>
> >>
> __________________________________________________________
> ___________
> >> ____________________________________________________
> >>
> >> 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.
> >>