[Babel-users] [babel] rather than ripemd160...

[STARK, BARBARA H]

FYI. IETF policies re "downrefs" in standards track RFCs is described in
https://tools.ietf.org/html/rfc3967 (and updated by https://tools.ietf.org/html/rfc8067).
In short, it's not prohibited, but careful review is required. 
Note RFC3967 Section 2 first bullet

   There are a number of circumstances in which an IETF document may
   need to make a normative reference to a document at a lower maturity
   level, but such a reference conflicts with Section 4.2.4 of
   [RFC2026].  For example:

   o  A standards track document may need to refer to a protocol or
      algorithm developed by an external body but modified, adapted, or
      profiled by an IETF informational RFC, for example, MD5 [RFC1321]
      and HMAC [RFC2104].  Note that this does not override the IETF's
      duty to see that the specification is indeed sufficiently clear to
      enable creation of interoperable implementations.

Barbara

> Dave Taht <dave.taht at gmail.com> writes:
> 
> > https://tools.ietf.org/html/rfc7693 
is informational. Is that good
> enough?
> 
> That's what I'm not sure about; it's neither standards track nor backed by a
> working group. So someone with more knowledge of IETF process than me
> needs to weigh in here :)
> -Toke
> 
> _______________________________________________
> babel mailing list
> babel at ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_babel&d=DwICAg&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=-
> 6LF6X6DzeRccquqfCJFAeSx31uwzB0oM82nApUzuPo&s=1QakSDy0dO0qZVEb
> YiyJb6tj_NKEToWqiVanTi-rv6k&e=