Support publication with the modification proposed.
Cheers,
Jeff
On Aug 14, 2020, 7:42 AM -0700, Behcet Sarikaya <sarikaya2012@xxxxxxxxx>, wrote:
--Hi all,I read the document.
On Wed, Aug 12, 2020 at 12:08 PM Bob Hinden <bob.hinden@xxxxxxxxx> wrote:Doing a quick read I wonder if this document is missing some discussion of MTUs for each of the carried protocols? It supports IPv4, Ethernet, and IPv6. All of these have some MTU limitations that are different.
Also the way the length field is defined, I don’t think this supports a full IPv6 packet. The IPv6 Payload Length field (16-bits) is the length of data after the IPv6 header.
Bob
I support Bob's comments, I think that such minor modifications are needed.The document is a good read for those who want to get familiar with 5G acronyms and what they mean from IETF point of view.Support publication after this modification.Behcet
> On Aug 12, 2020, at 8:58 AM, Ron Bonica <rbonica=40juniper..net@xxxxxxxxxxxxxx> wrote:
>
> +1
>
>
>
> Juniper Business Use Only
>
> -----Original Message-----
> From: last-call <last-call-bounces@xxxxxxxx> On Behalf Of Joel M. Halpern
> Sent: Wednesday, August 12, 2020 10:15 AM
> To: 'last-call@xxxxxxxx' <last-call@xxxxxxxx>; 'draft-allan-5g-fmc-encapsulation@xxxxxxxx' <draft-allan-5g-fmc-encapsulation@xxxxxxxx>
> Cc: 'ek.ietf@xxxxxxxxx' <ek.ietf@xxxxxxxxx>
> Subject: Re: [Last-Call] Last Call: <draft-allan-5g-fmc-encapsulation-04.txt> (5G Wireless Wireline Convergence User Plane Encapsulation (5WE)) to Informational RFC
>
> [External Email. Be cautious of content]
>
>
> The problem described in this draft is real. The solution seems to me to be the best compromise available for how to address the issue. I support publication of this document as an Informational RFC.
>
> Yours,
> Joel
>
>> -----Original Message-----
>> From: iesg-secretary@xxxxxxxx <iesg-secretary@xxxxxxxx>
>> Sent: Tuesday, 30 June 2020 12:18 AM
>> To: IETF-Announce <ietf-announce@xxxxxxxx>
>> Cc: ek.ietf@xxxxxxxxx; draft-allan-5g-fmc-encapsulation@xxxxxxxx
>> Subject: Last Call: <draft-allan-5g-fmc-encapsulation-04.txt> (5G
>> Wireless Wireline Convergence User Plane Encapsulation (5WE)) to
>> Informational RFC
>>
>> The IESG has received a request from an individual submitter to consider the following document: - '5G Wireless Wireline Convergence User Plane Encapsulation (5WE)'
>> <draft-allan-5g-fmc-encapsulation-04.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@xxxxxxxx mailing lists by 2020-07-27. Exceptionally, comments may be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>> As part of providing wireline access to the 5G Core (5GC), deployed
>> wireline networks carry user data between 5G residential gateways
>> and the 5G Access Gateway Function (AGF). The encapsulation used
>> needs to meet a variety of requirements including being able to
>> multiplex the traffic of multiple PDU sessions within a VLAN
>> delineated access circuit, to permit legacy equipment in the data
>> path to snoop certain packet fields, to carry 5G QoS information
>> associated with the data, and to be efficiently encoded. This memo
>> specifies an encapsulation that meets these requirements.
>
> --
> last-call mailing list
> last-call@xxxxxxxxx
> https://urldefense.com/v3/__https://www.ietf..org/mailman/listinfo/last-call__;!!NEt6yMaO-gk!V57aUA3TZXAcWjihH_iStbx8WKtbVk6zS3K71BbhWuI6qk-126R0VCAHbQR1wluO$
>
> --
> last-call mailing list
> last-call@xxxxxxxxx
> https://www.ietf.org/mailman/listinfo/last-call
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
