Howdy, A couple of things about this specification confuse me, and I'd appreciate enlightenment from the authors. The first is that the document spends a fair amount of time setting up the context in which GETS or other services might use resource priority and how this mechanism relates to the SIP resource-priority header. In Section 4.2.3, though, the documents says: An LS MAY add the ResourcePriority attribute when propagating routing objects to an LS in another domain. The inclusion of the ResourcePriority attribute is a matter of local administrative policy. Should the reader assume that this local administrative policy will follow one of the policy approaches discussed in Section 2? If so, should this be stated explicitly? If not, is the text in Section 2 appropriate? The second is that relatively sparseness of the Security Considerations, which at the moment read: The document defines a new attribute for the TRIP protocol and has no direct security considerations applied to it. However, the security considerations for TRIP and its messages remain the same and are articulated in Section 14 of [rfc3219]. Are there no security considerations for the removal of this header by LSes which fail to honor the requirement that an LS "MUST propagate the ResourcePriority attribute"? Are there any specific considerations (security or reliability) that apply when the Partial flag has been set by Location Server that does not recognize the attribute? Thanks for any insight, regards, Ted Hardie At 1:43 PM -0400 7/10/07, The IESG wrote: >The IESG has received a request from an individual submitter to consider >the following document: > >- 'TRIP Attribute for Resource Priority ' > <draft-carlberg-trip-attribute-rp-02.txt> as a Proposed Standard > >The IESG plans to make a decision in the next few weeks, and solicits >final comments on this action. Please send substantive comments to the >ietf@xxxxxxxx mailing lists by 2007-08-17. Exceptionally, >comments may be sent to iesg@xxxxxxxx instead. In either case, please >retain the beginning of the Subject line to allow automated sorting. > >The file can be obtained via >http://www.ietf.org/internet-drafts/draft-carlberg-trip-attribute-rp-02.txt > > >IESG discussion can be tracked via >https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13669&rfc_flag=0 > > >_______________________________________________ >IETF-Announce mailing list >IETF-Announce@xxxxxxxx >https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf