Ok, thanks. In DHCP there are still a few option-codes undefined, such as option-code: OPTION_MAP_PORTPARAMS (TBD4), etc… not sure if this has been assigned by IANA. But I need to look the transcript from the DHC folks first to see where is this heading.
For Radius it seems ok, I was confused by the ‘Type TBD’ in section 4.1, page 5. But I see now that the types are defined further below in the draft. Thanks again. Kris From: Sheng Jiang [mailto:[email protected]] Sent: Wednesday, December 12, 2012 5:19 PM To: Poscic, Kristian (Kristian); [email protected] Cc: [email protected] Subject: RE: dhcp/radius in MAT-E/T We did present draft-jiang-softwire-map-radius-02 in Atlanta and continue working on it. Since you state “there are many codes still missing”, if you can give me a detailed mail to explain what is missing, it might be very good contributions. Many thanks and best regards, Sheng From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Poscic, Kristian (Kristian) Sent: Thursday, December 13, 2012 7:03 AM To: [email protected]<mailto:[email protected]> Subject: [Softwires] dhcp/radius in MAT-E/T Has any further work been done on: draft-mdt-softwire-map-dhcp-option-03<http://datatracker.ietf.org/doc/draft-mdt-softwire-map-dhcp-option/> draft-jiang-softwire-map-radius-02<http://datatracker.ietf.org/doc/draft-jiang-softwire-map-radius/> There are many codes still missing in those two drafts. Last I remember was some discussion via emails where it was debated with DHC folks whether those options should be passed via DHCPv6 or not…I was wondering if those discussions have progressed in Atlanta. Thanks, Kris
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
