Media Type Specifications and Registration Procedures

The geophysics, geology and mechanics of slow fault slip

“…While a direct correlation between slow slip accelerations and some larger earthquakes can be documented (e.g., Uchida et al, 2016), most SSEs occur without subsequent large earthquakes. Thus, rather than being an inherent part of the earthquakenucleation process, the association of SSEs with subsequent earthquake ruptures may simply reflect triggering relationships similar to those between earthquakes (Freed, 2005). While improved observations of slow slip are not likely to lead to reliable short-term earthquake predictions, refined characterization of slow slip episodes and their relation to large earthquakes continues to be a promising area of research (Obara and Kato, 2016).…”

“…3c, Taira et al, 2014, Araki et al, 2017, Wallace et al, 2017. Together with other postseismic relaxation mechanisms, slow slip of either type can enhance static stress changes at large distances from a mainshock and trigger subsequent events (e.g., Hearn et al, 2002, Freed, 2005.…”

Deprecating the "X-" Prefix and Similar Constructs in Application Protocols

“…One of the original reasons for segregation of name spaces into standardized and unstandardized areas was the perceived difficulty of registering names. However, the solution to that problem has been simpler registration rules, such as those provided by [RFC3864] and [RFC4288]. As explained in [RFC4288]:…”

“…When it is extremely unlikely that some parameters will ever be standardized. In this case, implementation-specific and privateuse parameters could at least incorporate the organization's name (e.g., "ExampleInc-foo" or, consistent with [RFC4288], "VND.ExampleInc.foo") or primary domain name (e.g., "com.example.foo" or a Uniform Resource Identifier [RFC3986] such as "http://example.com/foo"). In rare cases, truly experimental parameters could be given meaningless names such as nonsense words, the output of a hash function, or Universally Unique Identifiers (UUIDs) [RFC4122].…”

Media Type Registration of RTP Payload Formats

“…RFC 4288 [1] defines media type specification and registration procedures that use the Internet Assigned Numbers Authority (IANA) as a central registry. That document covers general requirements independent of particular application environments and transport modes.…”