Hi, I read draft-ietf-opsawg-capwap-hybridmac-02.txt. I think it is well-written and addresses the issue described.
There are a few minor editorial issues: s/the the/the/ s/unamabigously/unambigously/ s/Figure 1 quoted/Figure 1 is quoted/ s/in Figure 1/in Figure 1./ s/regsitered/registered/ I would write in section 5. Security Considerations following: "This document does not introduce any new security risks compared to [RFC5416]. The security considerations described in [RFC5416] apply here as well." Regards, Mehmet > -----Original Message----- > From: OPSAWG [mailto:[email protected]] On Behalf Of ext Warren > Kumari > Sent: Monday, April 07, 2014 6:45 PM > To: [email protected]; [email protected] > Subject: [OPSAWG] Start of WGLC for draft-ietf-opsawg-capwap-hybridmac > > Dear opsawg WG, > > The authors of draft-ietf-opsawg-capwap-hybridmac have indicated that > they believe that the document is ready, and have asked for Working > Group Last Call. > > The draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-hybridmac/ > > Please review this draft to see if you think it is ready for > publication > and send comments to the list, clearly stating your view. > > This WGLC ends Mon 21-Apr-2014. > > Thanks, > Warren Kumari > (as opsawg WG co-chair) > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
