<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD><TITLE>general question</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
PRE {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri>Roni,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>thank
you for replying.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri>>> Are you asking if the media type registration need to be
in the same document as the payload specification</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>Yes,
exactly.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri>>> Look in RFC 4855 ........ there it says that registration
and the payload specification can be different documents.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri>Indeed, but some may argue that RFC4855 is related to the RTP
(Real-time Transport Protocol) case only. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>RFC
4288, which is mote general, seems to state the opposite at par. 4.10:
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri> "Proposals for media types registered in the
standards tree by the IETF itself MUST be published as
RFCs."</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>So it
is still not clear (to me) if RFC 4855 is an exception to the general rule, or
not.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri>>> <SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
am not sure that I know of such cases...</SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>I
think you are right. After a closer examination of several cases, I have
always found a (sort of) media type registration in each of
them.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>Again,
I wonder if a media type can be registered </FONT></SPAN><SPAN
class=046463408-09032009><FONT face=Calibri>after the payload specification has
been published; it may not always be clear, at the payload specifications'
publication time, that a corresponding new media type is also
needed.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT face=Calibri>
Adriano</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046463408-09032009><FONT
face=Calibri></FONT></SPAN> </DIV><FONT face=Calibri></FONT><BR>
<DIV class=OutlookMessageHeader lang=it dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Da:</B> Roni Even [mailto:ron.even.tlv@gmail.com]
<BR><B>Inviato:</B> lunedě 9 marzo 2009 9.26<BR><B>A:</B> Santoni Adriano;
ietf-types@alvestrand.no<BR><B>Oggetto:</B> RE: general
question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Adriano,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
am not sure I fully understand your question. Are you asking if the media type
registration need to be in the same document as the payload
specification.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Look
in RFC 4855 (<A
href="http://tools.ietf.org/html/rfc4855">http://tools.ietf.org/html/rfc4855</A>)
for published specification, there it says that registration and the payload
specification can be different documents.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
am not sure that I know of such cases. In some cases there are RFC that update
the registration for example by adding parameters. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Regards<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Roni
Even<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
ietf-types-bounces@alvestrand.no [mailto:ietf-types-bounces@alvestrand.no] <B>On
Behalf Of </B>Santoni Adriano<BR><B>Sent:</B> Monday, March 09, 2009 9:05
AM<BR><B>To:</B> ietf-types@alvestrand.no<BR><B>Subject:</B> general
question<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'">Hello,</SPAN>
<o:p></o:p></P>
<P><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'">I have the following doubt,
and would like someone to enlighten me.</SPAN> <o:p></o:p></P>
<P><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'">Is it mandatory that a
media type registration be included in the RFC that defines such media
type?</SPAN> <o:p></o:p></P>
<P><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'">It seems to me, if I am not
mistaken, that there are several media types defined in RFCs which does not
contain an explicit media type registration….</SPAN><o:p></o:p></P>
<P><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'">TIA,</SPAN> <BR><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'"> Adriano</SPAN>
<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>