Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-12 Thread Martin Thomson
On Tue, May 12, 2020, at 22:32, Bob Harold wrote: > > How does the capport wg feel as a whole about this question? [MAC as > > identifier] > > I am also wondering the same thing. We did discuss this, if I recall. From memory, there were a few reasons not to go further: MAC randomization mea

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-12 Thread Kyle Larose
Hello, Thanks for the quick feedback On Mon, 11 May 2020 at 15:25, S Moonesamy wrote: > > 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 dra

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-12 Thread Bob Harold
On Tue, May 12, 2020 at 8:10 AM Kyle Larose wrote: > Hi Bob, > > Thanks for the quick feedback. > > > I am curious why section 3.4 does not consider the MAC Address as a > possible identifier? > > Its omission doesn't mean that the MAC Address is not a valid > identifier. One should evaluate it u

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-12 Thread Kyle Larose
Hi Bob, Thanks for the quick feedback. > I am curious why section 3.4 does not consider the MAC Address as a possible > identifier? Its omission doesn't mean that the MAC Address is not a valid identifier. One should evaluate it using the criteria provided in 3.2 and 3.3. When I wrote the skele

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-11 Thread Tirupachur Comerica, Subash
f.org" , "captive-portals@ietf.org" , "barryle...@gmail.com" Subject: Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC Editors, I've opened a few issues on the comments Subash indicated were still pending. I think that we can take

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-11 Thread Martin Thomson
guess so) Or does it coordinate with it? – > [Resolved, Please ignore] > > > > *From: *Captive-portals on behalf of > Bob Harold > *Date: *Monday, May 11, 2020 at 10:35 AM > *To: *"last-c...@ietf.org" > *Cc: *"capport-cha...@ietf.org" , > &

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-11 Thread S Moonesamy
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' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comment

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-11 Thread Tirupachur Comerica, Subash
-c...@ietf.org" Cc: "capport-cha...@ietf.org" , "draft-ietf-capport-architect...@ietf.org" , "captive-portals@ietf.org" , IETF-Announce , "barryle...@gmail.com" , Martin Thomson Subject: Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Infor

Re: [Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-11 Thread Bob Harold
I am curious why section 3.4 does not consider the MAC Address as a possible identifier? -- Bob Harold On Mon, May 11, 2020 at 12:56 PM The IESG wrote: > > The IESG has received a request from the Captive Portal Interaction WG > (capport) to consider the following document: - 'CAPPORT Archite

[Captive-portals] Last Call: (CAPPORT Architecture) to Informational RFC

2020-05-11 Thread The IESG
The IESG has received a request from the Captive Portal Interaction WG (capport) to consider the following document: - 'CAPPORT Architecture' 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 comme