Re: [iri] #76: Fix reference to RFC 5378

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [iri] #76: Fix reference to RFC 5378

iri issue tracker
#76: Fix reference to RFC 5378

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 this is just in the boilerplate from the xml2rfc and was fixed by picking
 a new IPR option

--
-------------------------+-------------------------
 Reporter:  evnikita2@…  |       Owner:  masinter@…
     Type:  defect       |      Status:  closed
 Priority:  trivial      |   Milestone:
Component:  4395bis      |     Version:
 Severity:  -            |  Resolution:  fixed
 Keywords:               |
-------------------------+-------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/76#comment:2>
iri <http://tools.ietf.org/wg/iri/>


Reply | Threaded
Open this post in threaded view
|

Re: [iri] #76: Fix reference to RFC 5378

Peter Saint-Andre-2
On 1/24/12 5:28 PM, iri issue tracker wrote:

> #76: Fix reference to RFC 5378
>
> Changes (by masinter@…):
>
>  * status:  new => closed
>  * resolution:   => fixed
>
>
> Comment:
>
>  this is just in the boilerplate from the xml2rfc and was fixed by picking
>  a new IPR option

Actually, this is replacing [RFC3978] with [RFC5378] at several places
in 4395bis...

Section 3.8

   Avoid names or other symbols that might cause problems with rights to
   use the name in IETF specifications and Internet protocols.  For
   example, be careful with trademark and service mark names.  (See
   Section 7.4 of [RFC3978].)

Section 6.2

   2.  Prepare a URI/IRI scheme registration template, as specified in
       Section 6.4.  The scheme registration template may be contained
       in an Internet Draft, submitted alone, or as part of some other
       permanently available, stable, protocol specification.  The
       template may also be submitted in some other form (as part of
       another document or as a stand-alone document), but the contents
       will be treated as an "IETF Contribution" under the guidelines of
       [RFC3978].

Section 11.1

   [RFC3978]  Bradner, S., "IETF Rights in Contributions", RFC 3978,
              March 2005.