…posed on the URI schemes allowed for this parameter, Content Identifier (CID) [ RFC2392 ], HTTP [ RFC2616 ], and HTTPS [ RFC2818 ] are the URI schemes most commonly used by current implementations. Example: DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": Project XYZ…

…mposed on the URI schemes allowed for this parameter, Content Identifier (CID) [RFC2392], HTTP [RFC2616], and HTTPS [RFC2818] are the URI schemes most commonly used by current implementations. Example: DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": Project XYZ Revi…

…mposed on the URI schemes allowed for this parameter, Content Identifier (CID) [RFC2392], HTTP [RFC2616], and HTTPS [RFC2818] are the URI schemes most commonly used by current implementations. Example: DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": Project XYZ Revi…

…posed on the URI schemes allowed for this parameter, Content Identifier (CID) [ RFC2392 ], HTTP [ RFC2616 ], and HTTPS [ RFC2818 ] are the URI schemes most commonly used by current implementations. Example: DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": Project XYZ…

…posed on the URI schemes allowed for this parameter, Content Identifier (CID) [ RFC2392 ], HTTP [ RFC2616 ], and HTTPS [ RFC2818 ] are the URI schemes most commonly used by current implementations. Example: DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": Project XYZ…

… URIs are the Message ID (MID) and the Content-ID (CID). These are defined in [ RFC2392 ]. Although [ RFC2392 ] allows referencing messages or MIME body parts in other MIME entities or stores, it is strongly RECOMMENDED that iMIP implementations include all referenced messages an…

…f URIs are the Message ID (MID) and the Content-ID (CID). These are defined in [RFC2392]. Although [RFC2392] allows referencing messages or MIME body parts in other MIME entities or stores, it is strongly RECOMMENDED that iMIP implementations include all referenced messages and b…

…f URIs are the Message ID (MID) and the Content-ID (CID). These are defined in [RFC2392]. Although [RFC2392] allows referencing messages or MIME body parts in other MIME entities or stores, it is strongly RECOMMENDED that iMIP implementations include all referenced messages and b…

… URIs are the Message ID (MID) and the Content-ID (CID). These are defined in [ RFC2392 ]. Although [ RFC2392 ] allows referencing messages or MIME body parts in other MIME entities or stores, it is strongly RECOMMENDED that iMIP implementations include all referenced messages an…

…-extension Provisional 14667 Dave_Thaler cid content identifier Permanent 15202 RFC2392 coap coap Permanent RFC7252 RFC7252 coap+tcp coap+tcp (see [ reviewer notes ]) Permanent RFC8323 RFC8323 coap+ws coap+ws (see [ reviewer notes ]) Permanent 24 RFC8323 RFC8323 coaps coaps Perma…

…-extension Provisional 14667 Dave_Thaler cid content identifier Permanent 15202 RFC2392 coap coap Permanent RFC7252 RFC7252 coap+tcp coap+tcp (see [ reviewer notes ]) Permanent RFC8323 RFC8323 coap+ws coap+ws (see [ reviewer notes ]) Permanent 24 RFC8323 RFC8323 coaps coaps Perma…

…-extension Provisional 14667 Dave_Thaler cid content identifier Permanent 15202 RFC2392 coap coap Permanent RFC7252 RFC7252 coap+tcp coap+tcp (see [ reviewer notes ]) Permanent RFC8323 RFC8323 coap+ws coap+ws (see [ reviewer notes ]) Permanent 24 RFC8323 RFC8323 coaps coaps Perma…

…-extension Provisional 14667 Dave_Thaler cid content identifier Permanent 15202 RFC2392 coap coap Permanent RFC7252 RFC7252 coap+tcp coap+tcp (see [ reviewer notes ]) Permanent RFC8323 RFC8323 coap+ws coap+ws (see [ reviewer notes ]) Permanent 24 RFC8323 RFC8323 coaps coaps Perma…

…Pete Resnick Date Reported: 2024-04-25 Section 13.1.3 says: Content-ID Generic [RFC2392], [RFC2046], and [RFC5322] It should say: Content-ID Generic [RFC2046] Notes: Content-ID is defined in 2046, not in 2392 or 5322. IANA asked about this when 5322 was being obsoleted and wanted…

…Pete Resnick Date Reported: 2024-04-25 Section 13.1.3 says: Content-ID Generic [RFC2392], [RFC2046], and [RFC5322] It should say: Content-ID Generic [RFC2046] Notes: Content-ID is defined in 2046, not in 2392 or 5322. IANA asked about this when 5322 was being obsoleted and wanted…