MIME-Version: 1.0
References: 
 <178323677375.203065.6100917375357340169@dt-datatracker-57b5d8f849-v5cht>
In-Reply-To: 
 <178323677375.203065.6100917375357340169@dt-datatracker-57b5d8f849-v5cht>
From: Carles Gomez Montenegro <carles.gomez@upc.edu>
Date: Sun, 5 Jul 2026 09:49:17 +0200
Message-ID: 
 <CAAUO2xyrPfwHcGmRny2chgxh31909N5_6MqCS1hOJOQUjphRpA@mail.gmail.com>
To: core <core@ietf.org>, DTN WG <dtn@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e09a190655d865f8"
Message-ID-Hash: CJLZG3DWDS42IDL7RKLCNRQUN5ILSAKT
Precedence: list
Reply-To: carles.gomez@upc.edu
Subject: =?utf-8?q?=5Bcore=5D_Fwd=3A_I-D_Action=3A_draft-ietf-core-coap-bp-04=2Etxt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/core/cujWu9P2IgjI-tHTEaic4xtHj-w>

--000000000000e09a190655d865f8
Content-Type: text/plain; charset="UTF-8"

Hi again,

Just to clarify, -03 contained a too long line that made the diff quite
useless (many thanks, Carsten, for the heads-up!).

Revision -04 addresses this. If interested, please use the following link
to check the actual set of updates against the version that was presented
in IETF 125 (revision -02):
https://author-tools.ietf.org/iddiff?url1=draft-ietf-core-coap-bp-02&url2=draft-ietf-core-coap-bp-04&difftype=--html

Cheers,

Carles and Anna


---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sun, 5 Jul 2026 at 09:33
Subject: [core] I-D Action: draft-ietf-core-coap-bp-04.txt
To: <i-d-announce@ietf.org>
Cc: <core@ietf.org>


Internet-Draft draft-ietf-core-coap-bp-04.txt is now available. It is a work
item of the Constrained RESTful Environments (CORE) WG of the IETF.

   Title:   Constrained Application Protocol (CoAP) over Bundle Protocol
(BP)
   Authors: Carles Gomez
            Anna Calveras
   Name:    draft-ietf-core-coap-bp-04.txt
   Pages:   36
   Dates:   2026-07-05

Abstract:

   The Bundle Protocol (BP) was designed to enable end-to-end
   communication in challenged networks.  The Constrained Application
   Protocol (CoAP), which was designed for constrained-node networks,
   may be a suitable application-layer protocol for the scenarios where
   BP is used.  This document specifies how CoAP is carried over BP.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-coap-bp/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-bp-04

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-core-coap-bp-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
core mailing list -- core@ietf.org
To unsubscribe send an email to core-leave@ietf.org

--000000000000e09a190655d865f8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi again,</div><div><br></div><div>Just to clarify, -=
03 contained a too long line that made the diff quite useless (many thanks,=
 Carsten, for the heads-up!).</div><div><br></div><div>Revision -04 address=
es this. If interested, please use the following link to check the actual s=
et of updates against the version that was presented in IETF 125 (revision =
-02):</div><div><a href=3D"https://author-tools.ietf.org/iddiff?url1=3Ddraf=
t-ietf-core-coap-bp-02&amp;url2=3Ddraft-ietf-core-coap-bp-04&amp;difftype=
=3D--html">https://author-tools.ietf.org/iddiff?url1=3Ddraft-ietf-core-coap=
-bp-02&amp;url2=3Ddraft-ietf-core-coap-bp-04&amp;difftype=3D--html</a></div=
><div><br></div><div>Cheers,</div><div><br></div><div>Carles and Anna</div>=
<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>=
<div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" =
class=3D"gmail_attr">---------- Forwarded message ---------<br>From: <span =
dir=3D"auto">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-draft=
s@ietf.org</a>&gt;</span><br>Date: Sun, 5 Jul 2026 at 09:33<br>Subject: [co=
re] I-D Action: draft-ietf-core-coap-bp-04.txt<br>To:  &lt;<a href=3D"mailt=
o:i-d-announce@ietf.org">i-d-announce@ietf.org</a>&gt;<br>Cc:  &lt;<a href=
=3D"mailto:core@ietf.org">core@ietf.org</a>&gt;<br></div><br><br>Internet-D=
raft draft-ietf-core-coap-bp-04.txt is now available. It is a work<br>
item of the Constrained RESTful Environments (CORE) WG of the IETF.<br>
<br>
=C2=A0 =C2=A0Title:=C2=A0 =C2=A0Constrained Application Protocol (CoAP) ove=
r Bundle Protocol (BP)<br>
=C2=A0 =C2=A0Authors: Carles Gomez<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Anna Calveras<br>
=C2=A0 =C2=A0Name:=C2=A0 =C2=A0 draft-ietf-core-coap-bp-04.txt<br>
=C2=A0 =C2=A0Pages:=C2=A0 =C2=A036<br>
=C2=A0 =C2=A0Dates:=C2=A0 =C2=A02026-07-05<br>
<br>
Abstract:<br>
<br>
=C2=A0 =C2=A0The Bundle Protocol (BP) was designed to enable end-to-end<br>
=C2=A0 =C2=A0communication in challenged networks.=C2=A0 The Constrained Ap=
plication<br>
=C2=A0 =C2=A0Protocol (CoAP), which was designed for constrained-node netwo=
rks,<br>
=C2=A0 =C2=A0may be a suitable application-layer protocol for the scenarios=
 where<br>
=C2=A0 =C2=A0BP is used.=C2=A0 This document specifies how CoAP is carried =
over BP.<br>
<br>
The IETF datatracker status page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-core-coap-bp/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ie=
tf-core-coap-bp/</a><br>
<br>
There is also an HTMLized version available at:<br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-bp-04=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/htm=
l/draft-ietf-core-coap-bp-04</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-core-coap=
-bp-04" rel=3D"noreferrer" target=3D"_blank">https://author-tools.ietf.org/=
iddiff?url2=3Ddraft-ietf-core-coap-bp-04</a><br>
<br>
Internet-Drafts are also available by rsync at:<br>
rsync.ietf.org::internet-drafts<br>
<br>
<br>
_______________________________________________<br>
core mailing list -- <a href=3D"mailto:core@ietf.org" target=3D"_blank">cor=
e@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:core-leave@ietf.org" targ=
et=3D"_blank">core-leave@ietf.org</a><br>
</div></div></div>

--000000000000e09a190655d865f8--