Re: [Captive-portals] Last Call: <draft-ietf-capport-architecture-08.txt> (CAPPORT Architecture) to Informational RFC

[S Moonesamy <[e-mail]>]

Hello,
At 09:54 AM 11-05-2020, The IESG wrote:
>The IESG has received a request from the Captive Portal Interaction WG
>(capport) to consider the following document: - 'CAPPORT Architecture'
>   <draft-ietf-capport-architecture-08.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

I took a quick look at the draft.  The third paragraph in the 
Introduction section states that the document standardizes an 
architecture for implementing captive portals.  Does it  meant that 
this draft is intended to be a standard?

The principles listed to guide the architecture looks more like 
requirements.  Anyone who has been at an airport understands that 
existing protocols are being intercepted, forged, broken, etc. to get 
to reach the user to go through the "captive" experience.  The 
"SHOULD NOT" (why are the words in uppercase?) comes out as a 
principle that "one should follow the existing standards".

What are there "MAY" principles?

This document is about the architecture.  Where does it provide for 
incremental migration?

On reading further, I would say that the draft is a mix of 
requirements and "solution" instead of a draft about architecture.

Regards,
S. Moonesamy