RE: [Seamoby] CT Requirements Comments from IESG
"Gary Kenward" <gkenward@nortelnetworks.com> Wed, 10 July 2002 17:05 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 NAA11350 for <seamoby-archive@odin.ietf.org>; Wed, 10 Jul 2002 13:05:08 -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 MAA20239; Wed, 10 Jul 2002 12:59:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20206 for <seamoby@optimus.ietf.org>; Wed, 10 Jul 2002 12:59:19 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11118 for <seamoby@ietf.org>; Wed, 10 Jul 2002 12:58:24 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g6AGwci15419; Wed, 10 Jul 2002 12:58:39 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <NYVCCD6H>; Wed, 10 Jul 2002 12:58:38 -0400
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4BFF@zcard031.ca.nortel.com>
From: Gary Kenward <gkenward@nortelnetworks.com>
To: 'James Kempf' <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: RE: [Seamoby] CT Requirements Comments from IESG
Date: Wed, 10 Jul 2002 12:58:34 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C22833.067B52C6"
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
What does natural language have to do with it? I am not a linguist, but information representations have syntax and semantics (and as a result, they have meaning, at the very least one would assume, to the originator of the information). 'useable' on the other hand, is a wide open term, that could be interpreted strictly (i.e. the information has to exactly conformant to the requirements for configuration of the destination router), or very loosely (i.e. "null" information could be interpreted as "useable", in the trivial sense). In other words, there would be no requirement. The intent of this requirement, which went through much debate over the meaning of "integrity", is that the CT protocol must preserve what was sent by the source. For me, stating that the integrity of the information was preserved was enough. The wg decided that "meaning" had to be preserved. I cannot think of an example where, if one preserves the syntax and the symbol values (i.e. the "bits") of a given piece of information, the semantics would be lost. But then, I'm not a linguist. Said another way, the bits of the payload of the CT protocol must arrive in the order they were sent, and without any errors. Whether the receiving AR can understand what the sender sent is not a CT issue. CT just transfers the context, it does not define it. Thus, it is not required that the CT protocol ensure "useability" at the destination. That is a problem for the source. The analogy would be a requirement that TCP ensure that the application could interpret the payload delivered to it. It's always perplexed me why this simple, and somewhat obvious requirement, has been subject to so much controversy. Gary > -----Original Message----- > From: James Kempf [mailto:kempf@docomolabs-usa.com] > Sent: July 10, 2002 12:09 > To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@ietf.org > Subject: Re: [Seamoby] CT Requirements Comments from IESG > > > Hmm. > > So since there is no natural language conversation going on > between these two routers, may I suggest that "meaning" is not a > sufficiently precise word to use in this context? > > How about something along the lines of "usable to establish > services on the new router" or something like that. > > jak > > ----- Original Message ----- > From: "Gary Kenward" <gkenward@nortelnetworks.com> > To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org> > Sent: Wednesday, July 10, 2002 7:08 AM > Subject: RE: [Seamoby] CT Requirements Comments from IESG > > > Main Entry: meanĀ·ing > Pronunciation: 'mE-ni[ng] > Function: noun > > 4 a : the logical connotation of a word or phrase > > ------------ > > I propose, for section 5.5.2, to replace "meaning" with > "original syntax and semantics", unless someone has a better > idea. > > Gary > *snip* > > > > > > > I suspect that is it. What is "meaning"? > > > > jak > > > > > > >
- [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