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

[Gonzalo Camarillo <[e-mail]>]

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] 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]
>>> Cc : [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] 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]
>>>>> Cc : [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://datatracker.ietf.org/doc/draft-henry-tsvwg-diffserv-to-qci/
>>>>>
>>>>> 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://mailarchive.ietf.org/arch/msg/tsvwg/r3jAeNPcz83K0nFyQD4yObJkC-
>>>>> 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  [phone]
>>>>> Torshamnsgatan 23           | Mobile [phone]
>>>>> SE-164 80 Stockholm, Sweden | mailto:
>>> [e-mail]
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 3gpp-ietf-coord mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>>>>
>>>>
>>> ______________________________________________________________
>>> ___________________________________________________________
>>>>
>>>> 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]
>>>> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>>>>
>>
>> _________________________________________________________________________________________________________________________
>>
>> 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]
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>