Re: [Seamoby] CT Requirements Comments from IESG
"James Kempf" <kempf@docomolabs-usa.com> Wed, 10 July 2002 22:16 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21929 for <seamoby-archive@odin.ietf.org>; Wed, 10 Jul 2002 18:16:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA13274; Wed, 10 Jul 2002 18:13:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA13245 for <seamoby@optimus.ietf.org>; Wed, 10 Jul 2002 18:13:34 -0400 (EDT)
Received: from fridge.docomolabs-usa.com (fwuser@key1.docomolabs-usa.com [216.98.102.225]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21848 for <seamoby@ietf.org>; Wed, 10 Jul 2002 18:12:39 -0400 (EDT)
Message-ID: <017e01c2285e$c8c5d380$4f6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Gary Kenward <gkenward@nortelnetworks.com>, seamoby@ietf.org
References: <9FBD322B7824D511B36900508BF93C9C01AA4C01@zcard031.ca.nortel.com>
Subject: Re: [Seamoby] CT Requirements Comments from IESG
Date: Wed, 10 Jul 2002 15:11:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit
It's not the same definition I suggest: 5.5.2 A context update MUST preserve the integrity, and thus the intended useability, of the context at each receiving AR. jak ----- Original Message ----- From: "Gary Kenward" <gkenward@nortelnetworks.com> To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org> Sent: Wednesday, July 10, 2002 11:31 AM Subject: RE: [Seamoby] CT Requirements Comments from IESG > A word is often defined as 4 bytes, or 32 bits :-) in many > computational architectures and programming languages. > > Neither here nor there, really. I'll wait for further > suggestions/comments on the working of 5.5.2 from the wg. > > Gary > > > -----Original Message----- > > From: James Kempf [mailto:kempf@docomolabs-usa.com] > > Sent: July 10, 2002 14:12 > > To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@ietf.org > > Subject: Re: [Seamoby] CT Requirements Comments from IESG > > > > > > "Word" or "phrase", from the definition you cite, typically > > applies to natural language. I have not heard anyone use that > > terminology for machine readable information, even in > > programming languages. > > > > jak > > > > ----- Original Message ----- > > From: "Gary Kenward" <gkenward@nortelnetworks.com> > > To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org> > > Sent: Wednesday, July 10, 2002 9:58 AM > > Subject: RE: [Seamoby] CT Requirements Comments from IESG > > > > > > *snip* > > > > _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] CT Requirements Comments from IESG James Kempf
- Re: [Seamoby] CT Requirements Comments from IESG Charles E. Perkins
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG Vijay Devarapalli
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- RE: [Seamoby] CT Requirements Comments from IESG Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] CT Requirements Comments from IESG Nakhjiri Madjid-MNAKHJI1
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Dirk.Trossen
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Dirk.Trossen
- RE: [Seamoby] CT Requirements Comments from IESG john.loughney
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- Re: [Seamoby] CT Requirements Comments from IESG Charles E. Perkins
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- RE: [Seamoby] CT Requirements Comments from IESG Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] CT Requirements Comments from IESG Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- RE: [Seamoby] CT Requirements Comments from IESG Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] CT Requirements Comments from IESG Gary Kenward
- [Seamoby] Section 5.5 Modifications James Kempf
- RE: [Seamoby] CT Requirements Comments from IESG Nakhjiri Madjid-MNAKHJI1