Re-send with correct RTG-DIR address > -----Original Message----- > From: Adrian Farrel [ mailto:adrian at olddog.co.uk] > Sent: 21 April 2016 12:35 > To: 'Stewart Bryant'; rtg-ads at ietf.org > Cc: RTG-DIR at tools.ietf.org; draft-ietf-teas-interconnected-te-info- > exchange at tools.ietf.org; teas at ietf.org; Jonathan.Hardwick at metaswitch.com; > jon.hudson at gmail.com; zhang.xian at huawei.com; 'BRUNGARD, DEBORAH A' > Subject: RE: RtgDir review of draft-ietf-teas-interconnected-te-info-exchange-04 > > Stewart, > > Many thanks for your time and kind words. > > Responses in line. > > Deborah, when in the process do you want to see an update? > > Cheers, > Adrian > > > Summary: > > I have some minor concerns about this document that I think should be > resolved > > before publication. > > > > Comments: > > This is an exceptionally well written document that will serve community well in > > understanding this problem. > > > > The first two minor comments are in many ways optional, but I think addressing > > them would be appreciated by those new to the subject. > > > > Major Issues: > > No major issues found. > > > > Minor Issues: > > > > In section 1.1.2 TE Metrics and TE Attributes, there appears to be no definition > of > > either term (either by reference of by value). A definition and in particular a > > distinction would be helpful to the reader less familiar with the subject. > > I think that you're right that some clarity could be added. The general description > of the combination of the two terms looks fine to me, but by presenting two > terms we do need to distinguish them and explain. I suspect that some examples > and a little more description will do the job. Mainly we need to characterise a TE > metric as a quantifiable value (including measurement) describing some property > of a link or node that can be used as part of TE routing or planning, while a TE > attribute is a wider term (i.e. including TE metric) that refers to any property or > characteristic of a link or node that can be used as part of TE routing or planning. > > > Regarding Section 1.1.8. Abstract Node or Virtual Node. It is unclear whether > these > > are synonyms, or if there is a distinction between them. > > Hmmm. During WG last call we were asked to add 1.1.8 to give a root for use of > these terms, although I chose to point at 3.5 and 4.2.2.1 for more details. But I > think I can add a distinction between the very similar terms. > > > Section 5.2 > > The text "(i.e., completely separate instances using different address)" is > > incomplete. I think that you have omitted the word "spaces". > > Yes. Thanks. > > > Nits: > > "2.4. Requesting Connectivity > > > > " This relationship between domains can be entirely under the control" > > > > I think that should be "The relationship" > > Ack > > > Section 6 the text "are arranged a set of small domains" I think should be > > "are arranged as a set of small domains" > > Ack > > > Section 10.1 para 3 duplicate word "the the" > > Ack