Re: [Last-Call] Last Call: <draft-allan-5g-fmc-encapsulation-07.txt> (5G Wireless Wireline Convergence User Plane Encapsulation (5WE)) to Informational RFC

On Fri, Feb 5, 2021 at 5:17 PM Abdussalam Baryun <abdussalambaryun@gmail.com>
wrote:

> Dear All,
>
> I still think it needs to be proposed standard (even after receiving
> explanation from authors) because it includes a different field than
> RFC2516 which is the QoS field, this field is used in 5WE (5G wireline user
> plane encapsulation), furthermore the format-TYPE used in this
> encapsulation is 0x01 for upstream (while in the daft it mentions that this
> is for downstream, please explain how?), This encapsulation will be used in
> both PPPoE handling and in 5WE handling.
>
> For this VER=2, ....I suggest two encapsulation TYPE, one for UL and one
> for DL as mentioned in [TS38.415], the TYPE=0x00 is downstream with RQI and
> PPI, and the TYPE=0x01 is the upstream without, so the Session ID field
> replaces the field of spare in [TS38.415]. The PPI field is important for
> IPv4/IPv6 services as mentioned in [TS23501 ] for DL encapsulations.
>
> The document needs to give information on the session stage
> (ethertype=0x8864) related to DL 5WE (or downstream) and UL 5WE (upstream).
> It SHOULD  not be similar to the RFC2516 section 6.
>
> The R bit and o bit should be changed for the UL encapsulations TO, RQI
> and PPI bit and adding PPP field.
>

sorry, the DL encapsulation need to add RQI, PPI, PPP filed, (TYPE=0x00).

>
> This document should mention the sending method per fields in the format,
> as mentioned in page9  [TS38.415]. The handling of sending and receiving
> bits, in 5WE may be different than PPPoE, but if the same needs to be
> mentioned in this document.
>
> Regarding to security consideration I don't think the protocol ID field is
> needed to be in the format, also the security section should mention the
> security architecture for 5WE, which may be by referencing TS33.501.
>
> Best Regards
> AB
>
>
> On Fri, Jan 22, 2021 at 4:53 PM The IESG <iesg-secretary@ietf.org> wrote:
>
>>
>> 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-07.txt> as Informational RFC
>>
>> This requests the start of a 2nd IETF Last Call with the intent of
>> expressly calling
>> attention to the IPR claim associated with this document
>> (https://datatracker.ietf.org/ipr/3663/).
>>
>> 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@ietf.org mailing lists by 2021-02-05. Exceptionally, comments
>> may
>> be sent to iesg@ietf.org 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 method
>>    specified in this document supports the multiplexing of traffic for
>>    multiple PDU sessions within a VLAN delineated access circuit,
>>    permits legacy equipment in the data path to inspect certain packet
>>    fields, carries 5G QoS information associated with the packet data,
>>    and provides efficient encoding. It achieves this by specific points
>>    of similarity with the RFC 2516 PPPoE data packet encapsulation.
>>
>>
>>
>>
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-allan-5g-fmc-encapsulation/
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>>    https://datatracker.ietf.org/ipr/3663/
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>