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

Re: terminology change

To: Andy Bierman <ietf@andybierman.com>
Subject: Re: terminology change
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
Date: Wed, 1 Feb 2006 05:43:26 +0100
Cc: "Netconf (E-mail)" <netconf@ops.ietf.org>
Fcc: =SENT
In-reply-to: <43E01AFF.4000304@andybierman.com>
Mail-followup-to: Andy Bierman <ietf@andybierman.com>, "Netconf (E-mail)" <netconf@ops.ietf.org>
References: <43E01AFF.4000304@andybierman.com>
Reply-to: j.schoenwaelder@iu-bremen.de
User-agent: Mutt/1.5.10i

On Tue, Jan 31, 2006 at 06:20:47PM -0800, Andy Bierman wrote:
 
> We are going back to our original term "transport mapping",
> which aligns with our architecture diagrams (which include
> the transport, rpc, operations, and application layers).

Thank you very much. Very strong support from me here.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>

Follow-Ups:
- RE: terminology change
  - From: "David B Harrington" <dbharrington@comcast.net>
- Re: terminology change
  - From: Andy Bierman <ietf@andybierman.com>

References:
- terminology change
  - From: Andy Bierman <ietf@andybierman.com>

Prev by Date: terminology change
Next by Date: RE: how people implement <filter> in netconf over SOAP?
Previous by thread: terminology change
Next by thread: Re: terminology change
Index(es):
- Date
- Thread