[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

 "http://www.w3.org/TR/html4/loose.dtd">




<li> "http://www.w3.org/TR/html4/loose.dtd"></li>
<li></li>
<li></li>
<li></li>
<li></li>
<li><li>&lt;!--x-content-type: multipart/alternative --&gt;</li></li>
<li><li>&lt;!--x-date: Fri, 4 Jan 2002 11:20:32 &amp;#45;0500 (EST) --&gt;</li></li>
<li><li>&lt;!--x-from-r13: &quot;Unel Yrajneq&quot; &lt;txrajneqNabegryargjbexf.pbz&gt; --&gt;</li></li>
<li><li>&lt;!--x-message-id: <a href="mailto:9FBD322B7824D511B36900508BF93C9C01AA473B%40zcard031.ca.nortel.com"><a href="mailto:9FBD322B7824D511B36900508BF93C9C01AA473B%40zcard031.ca.nortel.com">9FBD322B7824D511B36900508BF93C9C01AA473B@zcard031.ca.nortel.com</a></a> --&gt;</li></li>
<li><li>&lt;!--x-subject: RE: [Seamoby] Minutes of Meeting at IETF 52 --&gt;</li></li>
<li><li>&lt;address&gt;title: &lt;STRONG&gt;RE: [Seamoby] Minutes of Meeting at IETF 52&lt;/STRONG&gt;&lt;/ADDRESS&gt;</li></li>
<li><li>&lt;h1&gt;re: [Seamoby] Minutes of Meeting at IETF 52&lt;/h1&gt;</li></li>
<li><li>&lt;li&gt;&lt;em&gt;date&lt;/em&gt;: Fri, 4 Jan 2002 11:18:24 -0500 &lt;/LI&gt;</li></li>
<li><li>&lt;li&gt;&lt;em&gt;from&lt;/em&gt;: &quot;Gary Kenward&quot; &amp;lt;&lt;A HREF=&quot;mailto:<a href="mailto:gkenward%40nortelnetworks.com"><a href="mailto:gkenward%40nortelnetworks.com">gkenward@nortelnetworks.com</a></a>&quot;&gt;<a href="mailto:gkenward%40nortelnetworks.com"><a href="mailto:gkenward%40nortelnetworks.com">gkenward@nortelnetworks.com</a></a>&lt;/A&gt;&amp;gt;&lt;/LI&gt;</li></li>
<li><li>&lt;li&gt;&lt;em&gt;list-id&lt;/em&gt;: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting &amp;lt;seamoby.ietf.org&amp;gt;&lt;/LI&gt;</li></li>
<li><li>&lt;li&gt;&lt;em&gt;sender&lt;/em&gt;: &lt;A HREF=&quot;mailto:<a href="mailto:seamoby-admin%40ietf.org"><a href="mailto:seamoby-admin%40ietf.org">seamoby-admin@ietf.org</a></a>&quot;&gt;<a href="mailto:seamoby-admin%40ietf.org"><a href="mailto:seamoby-admin%40ietf.org">seamoby-admin@ietf.org</a></a>&lt;/A&gt;&lt;/LI&gt;</li></li>
<li><li>&lt;li&gt;&lt;em&gt;subject&lt;/em&gt;: RE: [Seamoby] Minutes of Meeting at IETF 52&lt;/LI&gt;</li></li>
<li><li>&lt;li&gt;&lt;em&gt;to&lt;/em&gt;: &quot;'George Tsirtsis'&quot; &amp;lt;&lt;A HREF=&quot;mailto:<a href="mailto:G.Tsirtsis%40flarion.com"><a href="mailto:G.Tsirtsis%40flarion.com">G.Tsirtsis@flarion.com</a></a>&quot;&gt;<a href="mailto:G.Tsirtsis%40flarion.com"><a href="mailto:G.Tsirtsis%40flarion.com">G.Tsirtsis@flarion.com</a></a>&lt;/A&gt;&amp;gt;, &quot;'James Kempf'&quot; &amp;lt;&lt;A HREF=&quot;mailto:<a href="mailto:kempf%40docomolabs-usa.com"><a href="mailto:kempf%40docomolabs-usa.com">kempf@docomolabs-usa.com</a></a>&quot;&gt;<a href="mailto:kempf%40docomolabs-usa.com"><a href="mailto:kempf%40docomolabs-usa.com">kempf@docomolabs-usa.com</a></a>&lt;/A&gt;&amp;gt;, &lt;A HREF=&quot;mailto:<a href="mailto:seamoby%40ietf.org"><a href="mailto:seamoby%40ietf.org">seamoby@ietf.org</a></a>&quot;&gt;<a href="mailto:seamoby%40ietf.org"><a href="mailto:seamoby%40ietf.org">seamoby@ietf.org</a></a>&lt;/A&gt;&lt;/LI&gt;</li></li>
<li><li>&lt;title&gt;re: [Seamoby] Minutes of Meeting at IETF 52&lt;/title&gt;</li></li>

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;George:&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp; Yes we agree, but I do not hear a recommendation for action that would&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;solve the problem of eliminating trivial requirements, while preventing&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;wheel spinning. I'm trying to avoid repeating how long we've been at these&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;requirements, and how many times we have re-visited the same issues (the&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;mobility issue was covered the first time way back when).&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp; I also agree with your observations about the requirements you have singled&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;out, except for 5.5.2. As you probably recall, 5.5.2 is compromise wording for&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;the very critical need to ensure that the context is transferred without introducing errors (significant errors? more then 1 error in 10000000 bits?&amp;lt;/FONT&amp;gt;&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;*sigh* *shrug*). And so, I'm not sure why you see it as being semi-irrelevant.&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Maybe you see 5.5.2 as being ambiguous? Sure it is, but are you suggesting &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;we go back 10 months, and spend another 5 weeks debating subjective terms for error control?&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp; Finally, I do want you to understand that I am not in opposition to your&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;point of view, I am simply trying to explain the circumstances. I suggest&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;that you post a specific request to the working group to remove the &amp;amp;quot;semi-irrelevant&amp;amp;quot; requirements, and dis-ambiguate the remaining requirements.&amp;lt;/FONT&amp;gt;&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;You have my support.&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Gary&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;BTW: is &amp;amp;quot;broken record&amp;amp;quot; a relevant phrase any more? would the more apropos&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;term be a &amp;amp;quot;wacked CD&amp;amp;quot;? my daughter loves to listen to music play on purposely&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;quot;broken records&amp;amp;quot; (&amp;amp;quot;played&amp;amp;quot; by DJ's of all things, on very expensive machines&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;designed specifically to permit &amp;amp;quot;scratching&amp;amp;quot; and &amp;amp;quot;skipping&amp;amp;quot;), so does this make a &amp;amp;quot;broken record&amp;amp;quot; a good thing? *smile*&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;-----Original Message-----&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;From: George Tsirtsis [&amp;lt;A HREF=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com&amp;quot&quot";>mailto:G.Tsirtsis@flarion.com&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com&amp;quot";>mailto:G.Tsirtsis@flarion.com&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com&quot";>mailto:G.Tsirtsis@flarion.com&quot</a>;&gt;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com";>mailto:G.Tsirtsis@flarion.com</a>&lt;/a&gt;&amp;lt;/A&amp;gt;]&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Sent: January 4, 2002 10:49&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;To: Kenward, Gary [WDLN2:AN10:EXCH]; 'James Kempf'; seamoby@ietf.org&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Subject: RE: [Seamoby] Minutes of Meeting at IETF 52&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;
&amp;lt;BR&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Gary,&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;We agree in essence but disagree on action...as it has been for some time on this issue. I will thus try once again and see how it goes.&amp;lt;/FONT&amp;gt;&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Data validation was at some point suggested....and unfortunately accepted as a requirement. After some thought and multiple complaints people realized that this can not be a requirement....yet the idea of *removing* the requirement was for some, to me still weird, reason dismissed as utterly impossible! The authors in an attempt to correct the situation reworded this and made non-validation a requirement which brought a smile to my face :) and the issue again on the table &amp;lt;/FONT&amp;gt;&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;I do not understand the reluctance of this group to *remove* requirements. Removing a requirement DOES NOT....I repeat DOES NOT mean that the thing removed is now illegal or must not be supported...it&amp;amp;nbsp; just means that a proposal does not HAVE to cover it to be a valid proposal.&amp;lt;/FONT&amp;gt;&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;This has resulted in a document littered with semi-irrelevant and ambiguous requirements such as:&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;quot;4.12 The context information to be transferred MUST be available at the AR performing the transfer, prior to the initiation of a given phase of the context transfer.&amp;lt;/FONT&amp;gt;&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;4.13 The context transfer solution WILL NOT verify the context information prior to transfer.&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;4.15 The context transfer solution MAY include methods for interworking with non-IETF mobility solutions. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;5.5.2 A context update MUST preserve the integrity, and thus the meaning, of the context at each receiving AR.&amp;amp;quot;&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;I sound like a broken record I know...sorry.&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp;&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;George&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;-----Original Message-----&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;From: Gary Kenward [&amp;lt;A HREF=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:gkenward@nortelnetworks.com&amp;quot&quot";>mailto:gkenward@nortelnetworks.com&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="mailto:gkenward@nortelnetworks.com&amp;quot";>mailto:gkenward@nortelnetworks.com&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:gkenward@nortelnetworks.com&quot";>mailto:gkenward@nortelnetworks.com&quot</a>;&gt;<a  rel="nofollow" href="mailto:gkenward@nortelnetworks.com";>mailto:gkenward@nortelnetworks.com</a>&lt;/a&gt;&amp;lt;/A&amp;gt;]&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Sent: Friday, January 04, 2002 3:11 PM&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;To: 'George Tsirtsis'; 'James Kempf'; seamoby@ietf.org&amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Subject: RE: [Seamoby] Minutes of Meeting at IETF 52&amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;
&amp;lt;BR&amp;gt;

&amp;lt;P&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;George: &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp; Clearly there is much confusion over this particular requirement, &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;and I promptly admit that it is odd. I am concerned that old issues &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;will continue to be re-hashed if we start throwing out decisions that &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;were made, in this case, almost a year ago. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp; Someone, early last year, suggested that ct should check to ensure &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;that the context it was sending was valid context. I cannot reproduce &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;the whole conversation, but yes, the suggestion was to check semantics &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;as well as syntax of the context. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp; I personally could not see how this validation function could be &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;provided without an enormous amount of complexity. Most of the participants &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;in this conversation agreed, and to avoid any further discussion (the &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;debate actually went on for a while), it was stated as a requirement that &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;the ct solution would not attempt to perform validation of the context. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;This still leaves open the possibility that a router manufacturer could &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;attempt validation (and probably should, to some degree, as part of the &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;building of the feature context). &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp; Given that the IETF defines protocols, and validation does not seem &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;to require a protocol capability, you are right in that this requirement &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;does not really belong. However, past experience has repeatedly shown that &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;this working group will repeatedly re-visit old issues if they are not &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;clearly capture. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;nbsp; Perhaps you, or someone else could think of better wording and propose &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;it. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;Gary &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;quot;To introduce something altogether new would mean to begin all over, to &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;become ignorant again, and to run the old, old risk of failing to learn.&amp;amp;quot; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;(Isaac Asimov) &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; -----Original Message----- &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; From: George Tsirtsis [&amp;lt;A HREF=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com&amp;quot&quot";>mailto:G.Tsirtsis@flarion.com&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com&amp;quot";>mailto:G.Tsirtsis@flarion.com&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com&quot";>mailto:G.Tsirtsis@flarion.com&quot</a>;&gt;<a  rel="nofollow" href="mailto:G.Tsirtsis@flarion.com";>mailto:G.Tsirtsis@flarion.com</a>&lt;/a&gt;&amp;lt;/A&amp;gt;] &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Sent: January 3, 2002 15:43 &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; To: 'James Kempf'; seamoby@ietf.org &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Subject: RE: [Seamoby] Minutes of Meeting at IETF 52 &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; James, &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; From the minutes.... &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;amp;quot;Section 4.13 expanded greatly. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Q: Is WILL NOT part of the standard terms? &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; A: No, is SHOULD be a MUST NOT. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Q: So if the CT solution verifies the CT info prior to &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; transfer it is NOT &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; acceptable? &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; A: We'll take that up on the mailing list.&amp;amp;quot; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; To remind you 4.13 is &amp;amp;quot;4.13 The context transfer solution &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; WILL NOT verify &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; the context information prior to transfer.&amp;amp;quot; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; The old &amp;amp;quot;SHOULD&amp;amp;quot; was clearly not acceptable. The new &amp;amp;quot;MUST &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; NOT&amp;amp;quot; suggestion &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; was an obvious and a bit funny :-) mistake...As I pointed out &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; long time ago &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; this requirement should just be removed...it just makes no &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; sense....if only &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; it was the only one... ooops! I did not say that :-0 &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; George &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; -----Original Message----- &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; From: James Kempf [&amp;lt;A HREF=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:kempf@docomolabs-usa.com&amp;quot&quot";>mailto:kempf@docomolabs-usa.com&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="mailto:kempf@docomolabs-usa.com&amp;quot";>mailto:kempf@docomolabs-usa.com&amp;quot</a>&lt;/a&gt;;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="mailto:kempf@docomolabs-usa.com&quot";>mailto:kempf@docomolabs-usa.com&quot</a>;&gt;<a  rel="nofollow" href="mailto:kempf@docomolabs-usa.com";>mailto:kempf@docomolabs-usa.com</a>&lt;/a&gt;&amp;lt;/A&amp;gt;] &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Sent: Thursday, January 03, 2002 7:24 PM &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; To: seamoby@ietf.org &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Subject: [Seamoby] Minutes of Meeting at IETF 52 &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Attached. There is a one week comment period, ending on January 10. &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp; jak &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; _______________________________________________ &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Seamoby mailing list &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; Seamoby@ietf.org &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;A HREF=&amp;quot;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot";>https://www1.ietf.org/mailman/listinfo/seamoby&amp;quot</a>&lt;/a&gt;; TARGET=&amp;quot;_blank&amp;quot;&amp;gt;&lt;a  rel=&quot;nofollow&quot; href=&quot;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby&quot";>https://www1.ietf.org/mailman/listinfo/seamoby&quot</a>;&gt;<a  rel="nofollow" href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>&lt;/a&gt;&amp;lt;/A&amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;BR&amp;gt;&amp;lt;FONT SIZE=2&amp;gt;&amp;amp;gt; &amp;lt;/FONT&amp;gt;
&amp;lt;/P&amp;gt;



&amp;lt;!--X-Body-of-Message-End--&amp;gt;
&amp;lt;!--X-MsgBody-End--&amp;gt;
&amp;lt;!--X-Follow-Ups--&amp;gt;
&amp;lt;hr&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;Follow-Ups&amp;lt;/strong&amp;gt;:
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;&amp;lt;a name=&amp;quot;00093&amp;quot; href=&amp;quot;msg00093.html&amp;quot;&amp;gt;[Seamoby] Removing CT Requirements&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&amp;lt;em&amp;gt;From:&amp;lt;/em&amp;gt; &amp;amp;quot;James Kempf&amp;amp;quot; &amp;amp;lt;kempf@docomolabs-usa.com&amp;amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;
&amp;lt;!--X-Follow-Ups-End--&amp;gt;
&amp;lt;!--X-References--&amp;gt;
&amp;lt;!--X-References-End--&amp;gt;
&amp;lt;!--X-BotPNI--&amp;gt;
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;Prev by Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg00091.html&amp;quot;&amp;gt;RE: [Seamoby] Minutes of Meeting at IETF 52&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Next by Date:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg00093.html&amp;quot;&amp;gt;[Seamoby] Removing CT Requirements&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Previous by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg00091.html&amp;quot;&amp;gt;RE: [Seamoby] Minutes of Meeting at IETF 52&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Next by thread:
&amp;lt;strong&amp;gt;&amp;lt;a href=&amp;quot;msg00093.html&amp;quot;&amp;gt;[Seamoby] Removing CT Requirements&amp;lt;/a&amp;gt;&amp;lt;/strong&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;Index(es):
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;mail75.html#00092&amp;quot;&amp;gt;&amp;lt;strong&amp;gt;Date&amp;lt;/strong&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;a href=&amp;quot;thrd74.html#00092&amp;quot;&amp;gt;&amp;lt;strong&amp;gt;Thread&amp;lt;/strong&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;

&amp;lt;!--X-BotPNI-End--&amp;gt;
&amp;lt;!--X-User-Footer--&amp;gt;
&amp;lt;!--X-User-Footer-End--&amp;gt;
&amp;lt;/body&amp;gt;
&amp;lt;/html&amp;gt;
&lt;/pre&gt;
&lt;!--X-Body-of-Message-End--&gt;
&lt;!--X-MsgBody-End--&gt;
&lt;!--X-Follow-Ups--&gt;
&lt;hr&gt;
&lt;!--X-Follow-Ups-End--&gt;
&lt;!--X-References--&gt;
&lt;!--X-References-End--&gt;
&lt;!--X-BotPNI--&gt;
&lt;ul&gt;
&lt;li&gt;Prev by Date:
&lt;strong&gt;&lt;a href=&quot;msg00090.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Next by Date:
&lt;strong&gt;&lt;a href=&quot;msg00092.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Previous by thread:
&lt;strong&gt;&lt;a href=&quot;msg00090.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Next by thread:
&lt;strong&gt;&lt;a href=&quot;msg00092.html&quot;&gt;[no subject]&lt;/a&gt;&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Index(es):
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;maillist.html#00091&quot;&gt;&lt;strong&gt;Date&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;threads.html#00091&quot;&gt;&lt;strong&gt;Thread&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;!--X-BotPNI-End--&gt;
&lt;!--X-User-Footer--&gt;
&lt;!--X-User-Footer-End--&gt;
&lt;/body&gt;
&lt;/html&gt;
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00090.html">[no subject]</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00092.html">[no subject]</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00090.html">[no subject]</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00092.html">[no subject]</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00091"><strong>Date</strong></a></li>
<li><a href="threads.html#00091"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>

Prev by Date: [no subject]
Next by Date: [no subject]
Previous by thread: [no subject]
Next by thread: [no subject]
Index(es):
- Date
- Thread