Re: [MEXT] the future of the MEXT working group

Hesham Soliman <[email protected]>
Newsgroups gmane.ietf.nemo,gmane.ietf.mext
Message-ID <CAE2D2B7.1D6CE%[email protected]>

Hi Charlie, 

>>I agree that the current 3GPP architecture is very complicated and may
>> not be optimal, but I don't think it is a good idea to change it in
>>IETF...
>
>I agree we can't "change" 3GPP architecture in the IETF, but
>we can respond to the needs which are evident from considering
>the 3GPP architecture.  It seems very few believe that LTE
>is really immune from further evolution and even significant
>change in the future.  If IETF does NOT respond to the needs made
>evident in current 3GPP specifications, we have little hope of
>proper integration into their future evolved designs.

=> I think we should all learn from the RFC 3314 experience where IETF
(IPv6 WG at the time) made clear recommendations to 3GPP about address
configuration and all the recommendations were adopted in the same
release. I know these are smaller recommendations but this happens all the
time and we shouldn't worry about achieving things before trying to get a
unified view and presenting it. RFC 3316 is another example, although it
was more of a consensus-based approach between the two organisations

Hesham

>
>Regards,
>Charlie P.
>_______________________________________________
>MEXT mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/mext
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.