Skip to main content

Last Call Review of draft-ietf-masque-connect-ip-08
review-ietf-masque-connect-ip-08-opsdir-lc-dunbar-2023-03-22-00

Request Review of draft-ietf-masque-connect-ip
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2023-03-15
Requested 2023-03-01
Authors Tommy Pauly , David Schinazi , Alex Chernyakhovsky , Mirja K├╝hlewind , Magnus Westerlund
I-D last updated 2023-03-22
Completed reviews Dnsdir Telechat review of -09 by R. (Miek) Gieben (diff)
Intdir Early review of -07 by Timothy Winters (diff)
Dnsdir Last Call review of -08 by R. (Miek) Gieben (diff)
Genart Last Call review of -08 by Vijay K. Gurbani (diff)
Artart Last Call review of -08 by Jean Mahoney (diff)
Tsvart Last Call review of -08 by Bob Briscoe (diff)
Secdir Last Call review of -09 by Nancy Cam-Winget (diff)
Opsdir Last Call review of -08 by Linda Dunbar (diff)
Intdir Telechat review of -09 by Timothy Winters (diff)
Httpdir Telechat review of -08 by Mark Nottingham (diff)
Intdir Telechat review of -10 by Dr. Joseph D. Touch (diff)
Dnsdir Telechat review of -09 by R. (Miek) Gieben (diff)
Assignment Reviewer Linda Dunbar
State Completed
Review review-ietf-masque-connect-ip-08-opsdir-lc-dunbar-2023-03-22
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/UO7sMUSuDE-jHJTzzYsWKkc8Ct8
Reviewed revision 08 (document currently at 13)
Result Serious Issues
Completed 2023-03-22
review-ietf-masque-connect-ip-08-opsdir-lc-dunbar-2023-03-22-00
Reviewer: Linda Dunbar
Review result: Has Issues

I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

Summary:
This document describes the method to encode IP packets with the HTTP frame.

Issue-1: HTTP frame itself is carried by an IP packet. If a client needs to
send data packets to its desired destinations (e.g., IP D, E, ) via the node
that acts as the IP Proxy shown in Figure 14, it can be much easier
accomplished by establishing an IP tunnel between the Client and the "IP Proxy
Node (i.e., the tunnel between IP-A and IP-B). The IP layer can already achieve
this goal natively. You don't need to put an IP packet inside an HTTP frame
which is a payload to an IP packet.

Issue-2: Address request capsule:
In order for the Client HTTP frame to reach the Proxy node, they both already
have the IP connection. What is the purpose of the Address request?

Issue-3: Section 4.7.3 Route_advertisement Capsule:
The widely deployed BGP can advertise the routes. You don't need another layer
to repeat the work.

Best Regards,
Linda Dunbar