I support it as-is, as a co-author. I am not aware of any IPRs related to t his draft.
Yakov. > --===============4714608224764060990== > Content-Language: en-US > Content-Type: multipart/alternative; > boundary="_000_CCDD516B3A1B8matthewboccialcatellucentcom_" > > --_000_CCDD516B3A1B8matthewboccialcatellucentcom_ > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > There have been a number of requests for the WG to adopt draft-rekhter-nvo3= > -vm-mobility-issues-03.txt as a working group draft. There has also been so= > me discussion on the list and in Atlanta as to whether VM mobility requirem= > ents and problem statement issues should be addressed in a stand alone draf= > t or as a part of the existing problem statement. There are also a number o= > f other drafts addressing this issue, so if draft-rekhter is adopted as a s= > tand alone working group document, then that will provide the base working = > group document into which any additional text would be added. > > In order to help the chairs determine how to progress on this issue, please= > can you indicate to the list: > > > * Do you support adoption of this draft as-is (yes/no)? > * If no, would you support adoption of this draft with changes, and if s= > o, what (e.g. more Layer 3 content)? > * If no, should all of the VM mobility problem statement be added to the= > NVO3 problem statement draft? > > Coincidentally, we are also polling for knowledge of any IPR that applies t= > o this draft, to ensure that IPR has been disclosed in compliance with IETF= > IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > If you are listed as a document author or contributor, please respond to th= > is email whether or not you are aware of any relevant IPR. The draft will n= > ot be adopted until a response has been received from each author and contr= > ibutor. > If you are on the NVO3 WG email list but are not listed as an author or con= > tributor, then please explicitly respond only if you are aware of any IPR t= > hat has not yet been disclosed in conformance with IETF rules. > > This call for consensus will close on Thursday 13th December 2012. > > Best regards > > Matthew and Benson > > --_000_CCDD516B3A1B8matthewboccialcatellucentcom_ > Content-Type: text/html; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > <html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:= > space; -webkit-line-break: after-white-space; "><div style=3D"color: rgb(0= > , 0, 0); font-family: Calibri, sans-serif; font-size: 14px; "><font face=3D= > "Calibri,sans-serif">There have been a number of requests for the WG to ado= > pt <span style=3D"white-space: pre-wrap;">draft-rekhter-nvo3-vm-mobili= ty-issues-03.txt as a working group draft. There has also been some discuss= > ion on the list and in Atlanta as to whether VM mobility requirements and p= > roblem statement issues should be addressed in a stand alone draft or as a = > part of the existing problem statement. There are also a number of other dr= > afts addressing this issue, so if draft-rekhter is adopted as a stand alone= > working group document, then that will provide the base working group docu= > ment into which any additional text would be added.</span></font></div><div= > style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size:= > 14px; "><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-= > wrap;"><br></span></font></div><div style=3D"color: rgb(0, 0, 0); font-fami= > ly: Calibri, sans-serif; font-size: 14px; "><font face=3D"Calibri,sans-seri= > f"><span style=3D"white-space: pre-wrap;">In order to help the chairs deter= > mine how to progress on this issue, please can you indicate to the list:</s= > pan></font></div><div style=3D"color: rgb(0, 0, 0); font-family: Calibri, s= > ans-serif; font-size: 14px; "><font face=3D"Calibri,sans-serif"><span style= > =3D"white-space: pre-wrap;"><br></span></font></div><ul style=3D"color: rgb= > (0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; "><li><font f= > ace=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">Do you su= > pport adoption of this draft as-is (yes/no)?</span></font></li><li><font fa= > ce=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">If no, wou= > ld you support adoption of this draft with changes, and if so, what (e.g. m= > ore Layer 3 content)?</span></font></li><li><span style=3D"color: rgb(0, 0,= > 0); font-family: Calibri, sans-serif; font-size: 14px; font-style: normal;= > font-weight: normal; text-decoration: none; ">If no, should all of the VM = > mobility problem statement be added to the NVO3 problem statement draft?</s= > pan></li></ul><div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans= > -serif; font-size: 14px; "><span style=3D"color: rgb(0, 0, 0); font-family:= > Calibri, sans-serif; font-size: 14px; font-style: normal; font-weight: nor= > mal; text-decoration: none; "><br></span></div><div style=3D"color: rgb(0, = > 0, 0); font-family: Calibri, sans-serif; font-size: 14px; "><div style=3D"f= > ont-family: Calibri; font-size: medium; "><font face=3D"Calibri,sans-serif"= > >Coincidentally, we are also polling for knowledge of any IPR that </f= > ont><span style=3D"font-family: Calibri, sans-serif; ">applies to this draf= > t, to ensure that IPR has been disclosed in </span><span style=3D"font= > -family: Calibri, sans-serif; ">compliance with IETF IPR rules (see RFCs 39= > 79, 4879, 3669 and 5378 for more details).</span></div><div style=3D"font-f= > amily: Calibri; font-size: medium; "><font face=3D"Calibri,sans-serif">If y= > ou are listed as a document author or contributor, please respond </fo= > nt><span style=3D"font-family: Calibri, sans-serif; ">to this email whether= > or not you are aware of any relevant IPR. The </span><font face=3D"Ca= > libri,sans-serif">draft will not be adopted until a response has been recei= > ved from each </font><span style=3D"font-family: Calibri, sans-serif; = > ">author and contributor.</span></div><div style=3D"font-family: Calibri; f= > ont-size: medium; "><font face=3D"Calibri,sans-serif">If you are on the NVO= > 3 WG email list but are not listed as an author </font><span style=3D"= > font-family: Calibri, sans-serif; ">or contributor, then please explicitly = > respond only if you are aware </span><span style=3D"font-family: Calib= > ri, sans-serif; ">of any IPR that has not yet been disclosed in conformance= > with IETF </span><span style=3D"font-family: Calibri, sans-serif; ">r= > ules.</span></div></div><div style=3D"color: rgb(0, 0, 0); font-family: Cal= > ibri; font-size: medium; "><span style=3D"font-family: Calibri, sans-serif;= > "><br></span></div><div><font face=3D"Calibri,sans-serif">This call for co= > nsensus will close on Thursday 13th December 2012.</font></div><d= > iv><font face=3D"Calibri,sans-serif"><br></font></div><div style=3D"color: = > rgb(0, 0, 0); font-family: Calibri; font-size: medium; "><span style=3D"fon= > t-family: Calibri, sans-serif; ">Best regards</span></div><div style=3D"col= > or: rgb(0, 0, 0); font-family: Calibri; font-size: medium; "><span style=3D= > "font-family: Calibri, sans-serif; "><br></span></div><div style=3D"color: = > rgb(0, 0, 0); font-family: Calibri; font-size: medium; "><span style=3D"fon= > t-family: Calibri, sans-serif; ">Matthew and Benson</span></div></body></ht= > ml> > > --_000_CCDD516B3A1B8matthewboccialcatellucentcom_-- > > --===============4714608224764060990== > Content-Type: text/plain; charset="us-ascii" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 > > --===============4714608224764060990==-- _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
