Hi Sabine, Thanks a lot for the suggestions. Please see below.
On Thu, Jul 4, 2013 at 10:18 AM, RANDRIAMASY, SABINE (SABINE) < [email protected]> wrote: > Hi Richard,**** > > ** ** > > Thanks a lot for your updates that all perfectly address my comments and > clarify a lot. I have inserted suggestions inline, on your update on > “[Page 27] §8.5.3 Example” and leave it up to you to use them. Their > purpose is to clarify from the beginning the fact that a Cost Type name is > local to an IRD and the names listed in the “meta” member are not > necessarily supported by all applicable resources entries. **** > > Thanks**** > > Sabine**** > > ** ** > > ** ** > > *De :* [email protected] [mailto:[email protected]] *De la part de > * Y. Richard Yang > *Envoyé :* lundi 1 juillet 2013 06:17 > *À :* RANDRIAMASY, SABINE (SABINE) > *Cc :* [email protected] > *Objet :* Re: [alto] draft-ietf-alto-protocol-16 - minor comments**** > > ** ** > > Hi Sabine,**** > > ** ** > > Thanks a lot for the excellent comments! Please see below.**** > > ** ** > > On Mon, Jun 24, 2013 at 1:02 PM, RANDRIAMASY, SABINE (SABINE) < > [email protected]> wrote:**** > > Dear all,**** > > **** > > While going through the latest update, I have listed some minor comments > and typos and suggest some re-phrasings below, in particular in paragraphs > on new features such as the new cost type and the in/re-direction to other > IRDs. I also attached a text file with the comments. **** > > Hoping it helps. **** > > Sabine**** > > **** > > **** > > ---------------------------------------**** > > COMMENTS ON draft-ietf-alto-protocol-16**** > > ---------------------------------------**** > > **** > > **** > > - everything in ++ indicates ADDED text, including white space**** > > - everything in -- indicated REMOVED text**** > > **** > > **** > > [Page 27] §8.5.3 Example**** > > The example IRD exposes a capability called "cost-type-name" that is not > introduced before and it would help to add some sentences to better > distinguish the roles of "cost-type-name" and "cost-type". Especially as > the combination of cost metric and cost mode into cost type is new to > people who already coded an ALTO Client. Besides, the field "cost-type" of > the meta member defines the cost type names but also specifies their > members. So I propose to add some text after the example IRD and before > sentence "Specifically, the "meta" member of the example IRD defines....", > that would look like: **** > > **** > > "When an ALTO Client wants to fetch the Cost Types supported at the uris > listed in the ALTO Server, it should look after string "cost-type-names". > The values of "cost-type-names" indicate Cost Types whose Cost Metric and > Cost Mode are specified in the field "cost-type" of member "meta" of the > IRD. Specifically etc. ...". **** > > **** > > Good comment. Here is the new text based on your suggestion:**** > > ** ** > > Specifically, the "meta" member of the example IRD defines a**** > > field named "cost-types", which defines the names of cost**** > > types*[ +for this IRD+ ] * . For example, "num-routing" in the > example is the name**** > > that refers to a Cost Type with Cost Mode being "numerical" and**** > > Cost Metric being "routingcost". The value of "cost-types" is**** > > of type IRDMetaCostTypes defined below; see Section 9.6 for the > definition of CostType.**** > > ** > Good clarification. It is changed in svn. > ** > > The names defined in "cost-types" can be used in *[ -*the* - ] > [ +one or more+ ]* > Another good clarification. Fixed. Thanks a lot! Richard
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
