It works for me. Thanks, Yiu
On 7/17/13 5:23 PM, "Suresh Krishnan" <[email protected]> wrote: >Hi Yiu, > As Tomek said we discussed this a bit in Orlando. If you are concerned >about this, we can do a short call on the list and follow up at the >meeting to see if there are any objections in the wg. Does that work for >you? > >Thanks >Suresh > >On 07/15/2013 12:48 PM, Lee, Yiu wrote: >> Woj, >> >> I am not objecting it. I just stated the new draft has been updated the >> scope w/o getting explicit consent from the ML. >> >> BR, >> Yiu >> >> From: Wojciech Dec <[email protected] <mailto:[email protected]>> >> Date: Monday, July 15, 2013 12:01 PM >> To: "Yiu L. LEE" <[email protected] >> <mailto:[email protected]>> >> Cc: Softwires-wg <[email protected] <mailto:[email protected]>> >> Subject: Re: [Softwires] Changes to DHCP MAP Option draft >> >> Yes. See Mail of July 8. So far your objection is the only one, although >> I don't quite see in it any technically grounded objection. >> A fair bit of discussions between authors (MAP and lw46), softwire & dhc >> chairs, and WG participants have taken place, and naturally will also be >> held in Berlin. >> >> Re-spinning draft versions is easy. >> >> >> On 15 July 2013 17:29, Lee, Yiu <[email protected] >> <mailto:[email protected]>> wrote: >> >> Since this is a WG draft, did the authors ask the WG to update this? >> When the WG accepted this draft, it was only for MAP. But seems the >> scope has been changed. This should start as an Individual draft. I >> will recommend to revert back to the last version and present this >> in Berlin to replace the MAP draft if the WG agrees with it. >> >> >> From: Wojciech Dec <[email protected] >><mailto:[email protected]>> >> Date: Thursday, July 11, 2013 10:43 AM >> To: Qi Sun <[email protected] >> <mailto:[email protected]>> >> Cc: Softwires-wg <[email protected] <mailto:[email protected]>> >> Subject: Re: [Softwires] Changes to DHCP MAP Option draft >> >> >> Yes, there was a long thread started by Tomek. Given that the option >> is applicable beyond MAP a *suggestion* was to rename it. I'm >> personally ok either way. The "Softwire46" option is the currently >> proposed name. >> >> _______________________________________________ >> Softwires mailing list >> [email protected] <mailto:[email protected]> >> https://www.ietf.org/mailman/listinfo/softwires >> >> >> >> >> _______________________________________________ >> Softwires mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/softwires >> >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
