Hi Donald,
In my opinion, this draft is not only for PPPoE, but it can be used by IPoE, it mentions number of protocols to be used, the draft proposes a new encapsulation format structure for 5G.
On Sun, Jan 24, 2021 at 1:09 AM Donald Eastlake <d3e3e3@xxxxxxxxx> wrote:
Hi AB,On Sat, Jan 23, 2021 at 1:25 AM Abdussalam Baryun <abdussalambaryun@xxxxxxxxx> wrote:Also, I recommend referencing [RFC7042], and I expect that this draft should be proposed standard not informational,While I don't see a need to reference RFC 7042, it wouldn't hurt.
ok, just I thought it will be better to refer to our documents while making this draft go through our production.
This is targeted to Informational because (1) the original RFC specifying PPP over Ethernet (PPPoE, RFC 2516) was Informational and (2) the functional parts of this specification were derived in the BBF, not the IETF, but it needs to be an IETF stream document in order to create the registry for PPPoE version numbers. When an externally derived specification is published by the IETF, it is normally published as informational.
Yes RFC2516 is specified for PPPoE, and is not specifying IPoE. 2516 does not propose new field-format for identifying data of the internet, or has any equipment in its data path to identify IP packets. This draft does propose identifying IPv4/IPv6 datagram to 5G equipments. Therefore, I still think the draft should propose for standard, what do you reply?
Best Regards
AB
Thanks,
Donald
===============================
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e3e3@xxxxxxxxxBest RegardsABOn Sat, Jan 23, 2021 at 1:19 AM Donald Eastlake <d3e3e3@xxxxxxxxx> wrote:I support the approval and publication of this draft as an author
notwithstanding the IPR declaration concerning it. It needs to be
referenced by Broadband Forum (BBF) documents and an appropriate
registry needs to be set up to note the assignment of the relevant
code point.
Thanks,
Donald
===============================
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e3e3@xxxxxxxxx
On Fri, Jan 22, 2021 at 9:52 AM The IESG <iesg-secretary@xxxxxxxx> 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@xxxxxxxx mailing lists by 2021-02-05. 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 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/
>
>
>
>
>
>
--
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
