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

Re: hierarchical naming

To: abierman@cisco.com
Subject: Re: hierarchical naming
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Tue, 19 Mar 2002 17:50:07 +0100
Cc: sming@ops.ietf.org
In-reply-to: <5.1.0.14.2.20020319073812.024d37b8@fedex.cisco.com> (messagefrom Andy Bierman on Tue, 19 Mar 2002 07:47:28 -0800)
References: <5.1.0.14.2.20020314084113.0243b9b0@fedex.cisco.com><5.1.0.14.2.20020314055121.00aedf98@fedex.cisco.com><5.1.0.14.2.20020314055121.00aedf98@fedex.cisco.com><5.1.0.14.2.20020314084113.0243b9b0@fedex.cisco.com><5.1.0.14.2.20020318075858.024f4be8@fedex.cisco.com> <5.1.0.14.2.20020319073812.024d37b8@fedex.cisco.com>


>>>>> Andy Bierman writes:

Andy> It's unfortunate that we don't have a coordinated effort between
Andy> EOS and SMING, because the biggest advantage of this naming
Andy> scheme is the ability to create protocol technology that can
Andy> move any type of sub-aggregate. I believe these protocol
Andy> enhancements will exist some day, but only if the SMING WG lays
Andy> the groundwork first.

I actually agree with the first sentence in the last paragraph.

Regarding the second sentence in the last paragraph, I think we better
install a coordinated effort rather than doing it piecewise.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

References:
- Re: hierarchical naming
  - From: Andy Bierman <abierman@cisco.com>
- Re: hierarchical naming
  - From: Andy Bierman <abierman@cisco.com>
- Re: hierarchical naming
  - From: Andy Bierman <abierman@cisco.com>
- Re: hierarchical naming
  - From: Andy Bierman <abierman@cisco.com>

Prev by Date: Re: comments on draft-bierman-sming-ds-02.txt
Next by Date: thoughts on documentation reuse.
Previous by thread: Re: hierarchical naming
Next by thread: thoughts on documentation reuse.
Index(es):
- Date
- Thread