Acee Lindem | 4 Oct 2011 23:45
Picon
Favicon

OSPF TE Extensions for Delay, Loss, and Jitter (formerly known as OSPF Express Path)

We've discussed this draft at the last two IETFs and there seemed to be interest. We believe we sorted out the
positioning/overlap with the MPLS and CCAMP WGs and are now ready to accept it as a WG document. 
Does anyone have any objections? 

Here is a link to the current draft: http://www.ietf.org/id/draft-giacalone-ospf-te-express-path-02.txt

Thanks,
Acee and Abhay 
fu.xihua | 8 Oct 2011 07:43
Picon

Re: OSPF TE Extensions for Delay, Loss, and Jitter (formerly known as OSPF Express Path)


Hi Acee,

I have read through the draft. I support it as a WG document now.
Some authors from this draft cooperated with us in doing the framework document and sorting out the overlap work.
I just want to inform people who are interest in this topic also notice the work in MPLS WG.
http://tools.ietf.org/html/draft-fuxh-mpls-delay-loss-te-framework-02


Best Regards,

Xihua Fu


Acee Lindem <acee.lindem <at> ericsson.com>
发件人:  ospf-bounces <at> ietf.org

2011-10-05 05:45

收件人
OSPF List <ospf <at> ietf.org>
抄送
主题
[OSPF] OSPF TE Extensions for Delay, Loss, and Jitter (formerly known as OSPF Express Path)





We've discussed this draft at the last two IETFs and there seemed to be interest. We believe we sorted out the positioning/overlap with the MPLS and CCAMP WGs and are now ready to accept it as a WG document.
Does anyone have any objections?

Here is a link to the current draft: http://www.ietf.org/id/draft-giacalone-ospf-te-express-path-02.txt

Thanks,
Acee and Abhay
_______________________________________________
OSPF mailing list
OSPF <at> ietf.org
https://www.ietf.org/mailman/listinfo/ospf


<div>
<br>Hi Acee,
<br><br>I have read through the draft. I support
it as a WG document now.
<br>Some authors from this draft cooperated
with us in doing the framework document and sorting out the overlap work.
<br>I just want to inform people who are
interest in this topic also notice the work in MPLS WG.
<br>http://tools.ietf.org/html/draft-fuxh-mpls-delay-loss-te-framework-02

<br><br><br>
Best Regards,<br><br>
Xihua Fu
<br><br><br><table width="100%"><tr valign="top">
<td width="35%">Acee Lindem &lt;acee.lindem <at> ericsson.com&gt;

<br>&#21457;&#20214;&#20154;: &nbsp;ospf-bounces <at> ietf.org
<p>2011-10-05 05:45
</p>
</td>
<td width="64%">
<table width="100%">
<tr valign="top">
<td>
<div align="right">&#25910;&#20214;&#20154;</div>
</td>
<td>OSPF List &lt;ospf <at> ietf.org&gt;
</td>
</tr>
<tr valign="top">
<td>
<div align="right">&#25220;&#36865;</div>
</td>
<td>
</td>
</tr>
<tr valign="top">
<td>
<div align="right">&#20027;&#39064;</div>
</td>
<td>[OSPF] OSPF TE Extensions for Delay,
Loss, and Jitter (formerly known as OSPF Express Path)</td>
</tr>
</table>
<br><table><tr valign="top">
<td>
</td>
<td></td>
</tr></table>
<br>
</td>
</tr></table>
<br><br><br>We've discussed this draft at the last two IETFs and
there seemed to be interest. We believe we sorted out the positioning/overlap
with the MPLS and CCAMP WGs and are now ready to accept it as a WG document.
<br>
Does anyone have any objections? <br><br>
Here is a link to the current draft: http://www.ietf.org/id/draft-giacalone-ospf-te-express-path-02.txt<br><br>
Thanks,<br>
Acee and Abhay <br>
_______________________________________________<br>
OSPF mailing list<br>
OSPF <at> ietf.org<br>
https://www.ietf.org/mailman/listinfo/ospf<br><br>
<br>
</div>
RFC Errata System | 11 Oct 2011 02:51
Favicon

[Editorial Errata Reported] RFC5709 (2989)


The following errata report has been submitted for RFC5709,
"OSPFv2 HMAC-SHA Cryptographic Authentication".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5709&eid=2989

--------------------------------------
Type: Editorial
Reported by: Dai Wenjie (David Jet) <dai.wenjie <at> zte.com.cn>

Section: 3.

Original Text
-------------
   With the additions in this document, the currently valid algorithms
   (including mode) for OSPFv2 Cryptographic Authentication include:

           Keyed-MD5               (defined in RFC 2328, Appendix D)

Corrected Text
--------------
   With the additions in this document, the currently valid algorithms
   (including mode) for OSPFv2 Cryptographic Authentication include:

           Keyed-MD5               (defined in RFC 2328, Appendix D)

Notes
-----
The link 'Appendix D' referenced is incorrect. It is now
'http://tools.ietf.org/html/rfc5709#appendix-D', and it should be 'http://tools.ietf.org/html/rfc2328#appendix-D'.
Pay attention to the difference of the numbers in links,please.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5709 (draft-ietf-ospf-hmac-sha-07)
--------------------------------------
Title               : OSPFv2 HMAC-SHA Cryptographic Authentication
Publication Date    : October 2009
Author(s)           : M. Bhatia, V. Manral, M. Fanto, R. White, M. Barnes, T. Li, R. Atkinson
Category            : PROPOSED STANDARD
Source              : Open Shortest Path First IGP
Area                : Routing
Stream              : IETF
Verifying Party     : IESG
Bhatia, Manav (Manav | 11 Oct 2011 02:59
Favicon

Re: [Editorial Errata Reported] RFC5709 (2989)

Yes, the link is incorrect in the HTML version of the RFC. I don't remember giving the URL and don't know how it
was inserted in the HTML version. Cant we just fix the HTML page to point to RFC 2328 Appendix D instead of
pointing to RFC 5709 Appendix D (which does not even exist!)?

There is no problem with the TXT version of the RFC. 

Cheers, Manav

> -----Original Message-----
> From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] 
> Sent: Tuesday, October 11, 2011 6:21 AM
> To: Bhatia, Manav (Manav); vishwas <at> ipinfusion.com; 
> mfanto <at> aegisdatasecurity.com; riw <at> cisco.com; 
> mjbarnes <at> cisco.com; tony.li <at> tony.li; rja <at> extremenetworks.com; 
> stbryant <at> cisco.com; adrian <at> olddog.co.uk; 
> acee.lindem <at> ericsson.com; akr <at> cisco.com
> Cc: dai.wenjie <at> zte.com.cn; ospf <at> ietf.org; rfc-editor <at> rfc-editor.org
> Subject: [Editorial Errata Reported] RFC5709 (2989)
> 
> 
> The following errata report has been submitted for RFC5709,
> "OSPFv2 HMAC-SHA Cryptographic Authentication".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5709&eid=2989
> 
> --------------------------------------
> Type: Editorial
> Reported by: Dai Wenjie (David Jet) <dai.wenjie <at> zte.com.cn>
> 
> Section: 3.
> 
> Original Text
> -------------
>    With the additions in this document, the currently valid 
> algorithms    (including mode) for OSPFv2 Cryptographic 
> Authentication include:             Keyed-MD5               
> (defined in RFC 2328, Appendix D)
> 
> Corrected Text
> --------------
>    With the additions in this document, the currently valid 
> algorithms    (including mode) for OSPFv2 Cryptographic 
> Authentication include:             Keyed-MD5               
> (defined in RFC 2328, Appendix D)
> 
> Notes
> -----
> The link 'Appendix D' referenced is incorrect. It is now 
> 'http://tools.ietf.org/html/rfc5709#appendix-D', and it 
> should be 'http://tools.ietf.org/html/rfc2328#appendix-D'. 
> Pay attention to the difference of the numbers in links,please.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, 
> please use "Reply All" to discuss whether it should be 
> verified or rejected. When a decision is reached, the 
> verifying party (IESG) can log in to change the status and 
> edit the report, if necessary. 
> 
> --------------------------------------
> RFC5709 (draft-ietf-ospf-hmac-sha-07)
> --------------------------------------
> Title               : OSPFv2 HMAC-SHA Cryptographic Authentication
> Publication Date    : October 2009
> Author(s)           : M. Bhatia, V. Manral, M. Fanto, R. 
> White, M. Barnes, T. Li, R. Atkinson
> Category            : PROPOSED STANDARD
> Source              : Open Shortest Path First IGP
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
> 
Acee Lindem | 11 Oct 2011 03:21

Re: [Editorial Errata Reported] RFC5709 (2989)

RFC-Editor(s),
Can you simply update the html link as Manav suggests?
Thanks,
Acee
On Oct 10, 2011, at 8:59 PM, Bhatia, Manav (Manav) wrote:

> Yes, the link is incorrect in the HTML version of the RFC. I don't remember giving the URL and don't know how
it was inserted in the HTML version. Cant we just fix the HTML page to point to RFC 2328 Appendix D instead of
pointing to RFC 5709 Appendix D (which does not even exist!)?
> 
> There is no problem with the TXT version of the RFC. 
> 
> Cheers, Manav
> 
>> -----Original Message-----
>> From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] 
>> Sent: Tuesday, October 11, 2011 6:21 AM
>> To: Bhatia, Manav (Manav); vishwas <at> ipinfusion.com; 
>> mfanto <at> aegisdatasecurity.com; riw <at> cisco.com; 
>> mjbarnes <at> cisco.com; tony.li <at> tony.li; rja <at> extremenetworks.com; 
>> stbryant <at> cisco.com; adrian <at> olddog.co.uk; 
>> acee.lindem <at> ericsson.com; akr <at> cisco.com
>> Cc: dai.wenjie <at> zte.com.cn; ospf <at> ietf.org; rfc-editor <at> rfc-editor.org
>> Subject: [Editorial Errata Reported] RFC5709 (2989)
>> 
>> 
>> The following errata report has been submitted for RFC5709,
>> "OSPFv2 HMAC-SHA Cryptographic Authentication".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5709&eid=2989
>> 
>> --------------------------------------
>> Type: Editorial
>> Reported by: Dai Wenjie (David Jet) <dai.wenjie <at> zte.com.cn>
>> 
>> Section: 3.
>> 
>> Original Text
>> -------------
>>   With the additions in this document, the currently valid 
>> algorithms    (including mode) for OSPFv2 Cryptographic 
>> Authentication include:             Keyed-MD5               
>> (defined in RFC 2328, Appendix D)
>> 
>> Corrected Text
>> --------------
>>   With the additions in this document, the currently valid 
>> algorithms    (including mode) for OSPFv2 Cryptographic 
>> Authentication include:             Keyed-MD5               
>> (defined in RFC 2328, Appendix D)
>> 
>> Notes
>> -----
>> The link 'Appendix D' referenced is incorrect. It is now 
>> 'http://tools.ietf.org/html/rfc5709#appendix-D', and it 
>> should be 'http://tools.ietf.org/html/rfc2328#appendix-D'. 
>> Pay attention to the difference of the numbers in links,please.
>> 
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, 
>> please use "Reply All" to discuss whether it should be 
>> verified or rejected. When a decision is reached, the 
>> verifying party (IESG) can log in to change the status and 
>> edit the report, if necessary. 
>> 
>> --------------------------------------
>> RFC5709 (draft-ietf-ospf-hmac-sha-07)
>> --------------------------------------
>> Title               : OSPFv2 HMAC-SHA Cryptographic Authentication
>> Publication Date    : October 2009
>> Author(s)           : M. Bhatia, V. Manral, M. Fanto, R. 
>> White, M. Barnes, T. Li, R. Atkinson
>> Category            : PROPOSED STANDARD
>> Source              : Open Shortest Path First IGP
>> Area                : Routing
>> Stream              : IETF
>> Verifying Party     : IESG
>> 
> _______________________________________________
> OSPF mailing list
> OSPF <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ospf

Acee Lindem | 12 Oct 2011 00:19
Picon
Favicon

Re: [Editorial Errata Reported] RFC5709 (2989)

Hi Alice,

Thanks for the information. In the hopes of dispensing of this matter quickly, I have opened a tools ticket
on this issue:

http://trac.tools.ietf.org/group/tools/trac/ticket/6

Can you close this errata as "Rejected"? If not, I'll advise Steward to do it (WG chairs don't have the
authority). 

Thanks,
Acee 

On Oct 11, 2011, at 5:51 PM, Alice Hagens wrote:

> Acee, Manav,
> 
> The HTML versions of RFCs available from tools.ietf.org (e.g., http://tools.ietf.org/html/rfc5709)
are created and maintained by the Tools Team, not the RFC Editor. They are automatically created by
running rfcmarkup (http://tools.ietf.org/tools/rfcmarkup/) on the text of the RFC. In short, the link
on http://tools.ietf.org/html/rfc5709 was automatically created based on parsing the string "RFC
2328, Appendix D".
> 
> As noted on http://www.rfc-editor.org/errata.php, errata are for the RFCs as available from
rfc-editor.org, e.g., http://www.rfc-editor.org/rfc/rfc5709.txt.
> 
> The verifiers (Area Directors) have the ability to edit the contents of the errata report.  Perhaps the
Corrected Text could convey the intended correction, maybe "Keyed-MD5  (defined in RFC 2328, Appendix D,
as updated by this document)", and the content of the Notes could be removed.
> 
> Thank you.
> RFC Editor/ah
> 
> On Oct 10, 2011, at 9:21 PM, Acee Lindem wrote:
> 
>> RFC-Editor(s),
>> Can you simply update the html link as Manav suggests?
>> Thanks,
>> Acee
>> On Oct 10, 2011, at 8:59 PM, Bhatia, Manav (Manav) wrote:
>> 
>>> Yes, the link is incorrect in the HTML version of the RFC. I don't remember giving the URL and don't know
how it was inserted in the HTML version. Cant we just fix the HTML page to point to RFC 2328 Appendix D instead
of pointing to RFC 5709 Appendix D (which does not even exist!)?
>>> 
>>> There is no problem with the TXT version of the RFC. 
>>> 
>>> Cheers, Manav
>>> 
>>>> -----Original Message-----
>>>> From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] 
>>>> Sent: Tuesday, October 11, 2011 6:21 AM
>>>> To: Bhatia, Manav (Manav); vishwas <at> ipinfusion.com; 
>>>> mfanto <at> aegisdatasecurity.com; riw <at> cisco.com; 
>>>> mjbarnes <at> cisco.com; tony.li <at> tony.li; rja <at> extremenetworks.com; 
>>>> stbryant <at> cisco.com; adrian <at> olddog.co.uk; 
>>>> acee.lindem <at> ericsson.com; akr <at> cisco.com
>>>> Cc: dai.wenjie <at> zte.com.cn; ospf <at> ietf.org; rfc-editor <at> rfc-editor.org
>>>> Subject: [Editorial Errata Reported] RFC5709 (2989)
>>>> 
>>>> 
>>>> The following errata report has been submitted for RFC5709,
>>>> "OSPFv2 HMAC-SHA Cryptographic Authentication".
>>>> 
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> http://www.rfc-editor.org/errata_search.php?rfc=5709&eid=2989
>>>> 
>>>> --------------------------------------
>>>> Type: Editorial
>>>> Reported by: Dai Wenjie (David Jet) <dai.wenjie <at> zte.com.cn>
>>>> 
>>>> Section: 3.
>>>> 
>>>> Original Text
>>>> -------------
>>>> With the additions in this document, the currently valid 
>>>> algorithms    (including mode) for OSPFv2 Cryptographic 
>>>> Authentication include:             Keyed-MD5               
>>>> (defined in RFC 2328, Appendix D)
>>>> 
>>>> Corrected Text
>>>> --------------
>>>> With the additions in this document, the currently valid 
>>>> algorithms    (including mode) for OSPFv2 Cryptographic 
>>>> Authentication include:             Keyed-MD5               
>>>> (defined in RFC 2328, Appendix D)
>>>> 
>>>> Notes
>>>> -----
>>>> The link 'Appendix D' referenced is incorrect. It is now 
>>>> 'http://tools.ietf.org/html/rfc5709#appendix-D', and it 
>>>> should be 'http://tools.ietf.org/html/rfc2328#appendix-D'. 
>>>> Pay attention to the difference of the numbers in links,please.
>>>> 
>>>> Instructions:
>>>> -------------
>>>> This errata is currently posted as "Reported". If necessary, 
>>>> please use "Reply All" to discuss whether it should be 
>>>> verified or rejected. When a decision is reached, the 
>>>> verifying party (IESG) can log in to change the status and 
>>>> edit the report, if necessary. 
>>>> 
>>>> --------------------------------------
>>>> RFC5709 (draft-ietf-ospf-hmac-sha-07)
>>>> --------------------------------------
>>>> Title               : OSPFv2 HMAC-SHA Cryptographic Authentication
>>>> Publication Date    : October 2009
>>>> Author(s)           : M. Bhatia, V. Manral, M. Fanto, R. 
>>>> White, M. Barnes, T. Li, R. Atkinson
>>>> Category            : PROPOSED STANDARD
>>>> Source              : Open Shortest Path First IGP
>>>> Area                : Routing
>>>> Stream              : IETF
>>>> Verifying Party     : IESG
>>>> 
>>> _______________________________________________
>>> OSPF mailing list
>>> OSPF <at> ietf.org
>>> https://www.ietf.org/mailman/listinfo/ospf
>> 
> 

Attachment (smime.p7s): application/pkcs7-signature, 3906 bytes
Hi Alice,

Thanks for the information. In the hopes of dispensing of this matter quickly, I have opened a tools ticket
on this issue:

http://trac.tools.ietf.org/group/tools/trac/ticket/6

Can you close this errata as "Rejected"? If not, I'll advise Steward to do it (WG chairs don't have the
authority). 

Thanks,
Acee 

On Oct 11, 2011, at 5:51 PM, Alice Hagens wrote:

> Acee, Manav,
> 
> The HTML versions of RFCs available from tools.ietf.org (e.g., http://tools.ietf.org/html/rfc5709)
are created and maintained by the Tools Team, not the RFC Editor. They are automatically created by
running rfcmarkup (http://tools.ietf.org/tools/rfcmarkup/) on the text of the RFC. In short, the link
on http://tools.ietf.org/html/rfc5709 was automatically created based on parsing the string "RFC
2328, Appendix D".
> 
> As noted on http://www.rfc-editor.org/errata.php, errata are for the RFCs as available from
rfc-editor.org, e.g., http://www.rfc-editor.org/rfc/rfc5709.txt.
> 
> The verifiers (Area Directors) have the ability to edit the contents of the errata report.  Perhaps the
Corrected Text could convey the intended correction, maybe "Keyed-MD5  (defined in RFC 2328, Appendix D,
as updated by this document)", and the content of the Notes could be removed.
> 
> Thank you.
> RFC Editor/ah
> 
> On Oct 10, 2011, at 9:21 PM, Acee Lindem wrote:
> 
>> RFC-Editor(s),
>> Can you simply update the html link as Manav suggests?
>> Thanks,
>> Acee
>> On Oct 10, 2011, at 8:59 PM, Bhatia, Manav (Manav) wrote:
>> 
>>> Yes, the link is incorrect in the HTML version of the RFC. I don't remember giving the URL and don't know
how it was inserted in the HTML version. Cant we just fix the HTML page to point to RFC 2328 Appendix D instead
of pointing to RFC 5709 Appendix D (which does not even exist!)?
>>> 
>>> There is no problem with the TXT version of the RFC. 
>>> 
>>> Cheers, Manav
>>> 
>>>> -----Original Message-----
>>>> From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] 
>>>> Sent: Tuesday, October 11, 2011 6:21 AM
>>>> To: Bhatia, Manav (Manav); vishwas <at> ipinfusion.com; 
>>>> mfanto <at> aegisdatasecurity.com; riw <at> cisco.com; 
>>>> mjbarnes <at> cisco.com; tony.li <at> tony.li; rja <at> extremenetworks.com; 
>>>> stbryant <at> cisco.com; adrian <at> olddog.co.uk; 
>>>> acee.lindem <at> ericsson.com; akr <at> cisco.com
>>>> Cc: dai.wenjie <at> zte.com.cn; ospf <at> ietf.org; rfc-editor <at> rfc-editor.org
>>>> Subject: [Editorial Errata Reported] RFC5709 (2989)
>>>> 
>>>> 
>>>> The following errata report has been submitted for RFC5709,
>>>> "OSPFv2 HMAC-SHA Cryptographic Authentication".
>>>> 
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> http://www.rfc-editor.org/errata_search.php?rfc=5709&eid=2989
>>>> 
>>>> --------------------------------------
>>>> Type: Editorial
>>>> Reported by: Dai Wenjie (David Jet) <dai.wenjie <at> zte.com.cn>
>>>> 
>>>> Section: 3.
>>>> 
>>>> Original Text
>>>> -------------
>>>> With the additions in this document, the currently valid 
>>>> algorithms    (including mode) for OSPFv2 Cryptographic 
>>>> Authentication include:             Keyed-MD5               
>>>> (defined in RFC 2328, Appendix D)
>>>> 
>>>> Corrected Text
>>>> --------------
>>>> With the additions in this document, the currently valid 
>>>> algorithms    (including mode) for OSPFv2 Cryptographic 
>>>> Authentication include:             Keyed-MD5               
>>>> (defined in RFC 2328, Appendix D)
>>>> 
>>>> Notes
>>>> -----
>>>> The link 'Appendix D' referenced is incorrect. It is now 
>>>> 'http://tools.ietf.org/html/rfc5709#appendix-D', and it 
>>>> should be 'http://tools.ietf.org/html/rfc2328#appendix-D'. 
>>>> Pay attention to the difference of the numbers in links,please.
>>>> 
>>>> Instructions:
>>>> -------------
>>>> This errata is currently posted as "Reported". If necessary, 
>>>> please use "Reply All" to discuss whether it should be 
>>>> verified or rejected. When a decision is reached, the 
>>>> verifying party (IESG) can log in to change the status and 
>>>> edit the report, if necessary. 
>>>> 
>>>> --------------------------------------
>>>> RFC5709 (draft-ietf-ospf-hmac-sha-07)
>>>> --------------------------------------
>>>> Title               : OSPFv2 HMAC-SHA Cryptographic Authentication
>>>> Publication Date    : October 2009
>>>> Author(s)           : M. Bhatia, V. Manral, M. Fanto, R. 
>>>> White, M. Barnes, T. Li, R. Atkinson
>>>> Category            : PROPOSED STANDARD
>>>> Source              : Open Shortest Path First IGP
>>>> Area                : Routing
>>>> Stream              : IETF
>>>> Verifying Party     : IESG
>>>> 
>>> _______________________________________________
>>> OSPF mailing list
>>> OSPF <at> ietf.org
>>> https://www.ietf.org/mailman/listinfo/ospf
>> 
> 

Vishwas Manral | 15 Oct 2011 01:32
Picon

Re: OSPF TE Extensions for Delay, Loss, and Jitter (formerly known as OSPF Express Path)

Hi Spencer,
 
I think we have discussed this within ourselves earlier, but I was wondering if you saw most of the loss on a link or on the device itself?
 
Thanks,
Vishwas
On Tue, Oct 4, 2011 at 2:45 PM, Acee Lindem <acee.lindem <at> ericsson.com> wrote:
We've discussed this draft at the last two IETFs and there seemed to be interest. We believe we sorted out the positioning/overlap with the MPLS and CCAMP WGs and are now ready to accept it as a WG document.
Does anyone have any objections?

Here is a link to the current draft: http://www.ietf.org/id/draft-giacalone-ospf-te-express-path-02.txt

Thanks,
Acee and Abhay
_______________________________________________
OSPF mailing list
OSPF <at> ietf.org
https://www.ietf.org/mailman/listinfo/ospf

<div>
<div>Hi Spencer,</div>
<div>&nbsp;</div>
<div>I think we have discussed this within ourselves earlier, but I was wondering&nbsp;if you saw most of the loss on a link or on the device itself?</div>
<div>&nbsp;</div>
<div>Thanks,</div>
<div>Vishwas<br>
</div>
<div class="gmail_quote">On Tue, Oct 4, 2011 at 2:45 PM, Acee Lindem <span dir="ltr">&lt;<a href="mailto:acee.lindem <at> ericsson.com" target="_blank">acee.lindem <at> ericsson.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">We've discussed this draft at the last two IETFs and there seemed to be interest. We believe we sorted out the positioning/overlap with the MPLS and CCAMP WGs and are now ready to accept it as a WG document.<br>
Does anyone have any objections?<br><br>Here is a link to the current draft: <a href="http://www.ietf.org/id/draft-giacalone-ospf-te-express-path-02.txt" target="_blank">http://www.ietf.org/id/draft-giacalone-ospf-te-express-path-02.txt</a><br><br>Thanks,<br>Acee and Abhay<br>_______________________________________________<br>OSPF mailing list<br><a href="mailto:OSPF <at> ietf.org" target="_blank">OSPF <at> ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/ospf" target="_blank">https://www.ietf.org/mailman/listinfo/ospf</a><br>
</blockquote>
</div>
<br>
</div>
Dean cheng | 19 Oct 2011 02:04
Favicon

posted - draft-ietf-ospf-ipv4-embedded-ipv6-routing-01

Dear OSPFers,

 

We posted draft-ietf-ospf-ipv4-embedded-ipv6-routing-01 last week

and comparing to the 00 text, the only change is a reference update

(RFC6145).

 

Please review and provide comments.

 

Thanks

Dean

<div>
<div class="Section1">
<p class="MsoNormal"><span>Dear OSPFers,<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>We
</span><span>posted
<a href="http://datatracker.ietf.org/doc/draft-ietf-ospf-ipv4-embedded-ipv6-routing/">
draft-ietf-ospf-ipv4-embedded-ipv6-routing-01</a> last week <p></p></span></p>
<p class="MsoNormal"><span>and comparing to the 00 text, the only change is a reference update<p></p></span></p>
<p class="MsoNormal"><span>(RFC6145).<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Please review and provide comments.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Thanks<p></p></span></p>
<p class="MsoNormal"><span>Dean<p></p></span></p>
</div>
</div>
Acee Lindem | 27 Oct 2011 01:48
Picon
Favicon

New Version Notification - draft-ietf-ospf-auth-trailer-ospfv3-08.txt

This version includes changes in response to the external reviews that have taken place since we completed
WG last call. A few things have been clarified and the following two items have been added:

    1. Mitigation of Cross Protocol Attacks by appending a protocol specific byte to the key. This will prevent
replay attacks when the same key is used by multiple protocols (and the sets of valid input packets
intercept). See sections 4.4 and 4.5.

    2. Recommendations for authentication key selection have been added to the "Security Considerations". 
See section 6.

Links to be the new version and a nicely annotated diff with the previous version are included in the
forwarded E-mail below.

Thanks,
Acee

Begin forwarded message:

From: "internet-drafts <at> ietf.org<mailto:internet-drafts <at> ietf.org>" <internet-drafts <at> ietf.org<mailto:internet-drafts <at> ietf.org>>
Date: October 26, 2011 6:19:35 PM EDT
To: "ospf-chairs <at> tools.ietf.org<mailto:ospf-chairs <at> tools.ietf.org>"
<ospf-chairs <at> tools.ietf.org<mailto:ospf-chairs <at> tools.ietf.org>>,
"draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org<mailto:draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org>"
<draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org<mailto:draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org>>,
"stbryant <at> cisco.com<mailto:stbryant <at> cisco.com>" <stbryant <at> cisco.com<mailto:stbryant <at> cisco.com>>
Subject: New Version Notification - draft-ietf-ospf-auth-trailer-ospfv3-08.txt

New version (-08) has been submitted for draft-ietf-ospf-auth-trailer-ospfv3-08.txt.
http://www.ietf.org/internet-drafts/draft-ietf-ospf-auth-trailer-ospfv3-08.txt

Diff from previous version:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-ospf-auth-trailer-ospfv3-08

IETF Secretariat.

Acee Lindem | 27 Oct 2011 01:53
Picon
Favicon

Re: New Version Notification - draft-ietf-ospf-auth-trailer-ospfv3-08.txt


Of course, I meant "intersect" rather than "intercept" below. In other words, a packet from one protocol
could potentially also represent a valid packet in another protocol and be replayed. 
Thanks,
Acee  

On Oct 26, 2011, at 7:48 PM, Acee Lindem wrote:

> This version includes changes in response to the external reviews that have taken place since we
completed WG last call. A few things have been clarified and the following two items have been added:
> 
>    1. Mitigation of Cross Protocol Attacks by appending a protocol specific byte to the key. This will
prevent replay attacks when the same key is used by multiple protocols (and the sets of valid input packets
intercept). See sections 4.4 and 4.5.
> 
>    2. Recommendations for authentication key selection have been added to the "Security Considerations". 
See section 6.
> 
> Links to be the new version and a nicely annotated diff with the previous version are included in the
forwarded E-mail below.
> 
> Thanks,
> Acee
> 
> 
> 
> 
> Begin forwarded message:
> 
> From: "internet-drafts <at> ietf.org<mailto:internet-drafts <at> ietf.org>" <internet-drafts <at> ietf.org<mailto:internet-drafts <at> ietf.org>>
> Date: October 26, 2011 6:19:35 PM EDT
> To: "ospf-chairs <at> tools.ietf.org<mailto:ospf-chairs <at> tools.ietf.org>"
<ospf-chairs <at> tools.ietf.org<mailto:ospf-chairs <at> tools.ietf.org>>,
"draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org<mailto:draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org>"
<draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org<mailto:draft-ietf-ospf-auth-trailer-ospfv3 <at> tools.ietf.org>>,
"stbryant <at> cisco.com<mailto:stbryant <at> cisco.com>" <stbryant <at> cisco.com<mailto:stbryant <at> cisco.com>>
> Subject: New Version Notification - draft-ietf-ospf-auth-trailer-ospfv3-08.txt
> 
> New version (-08) has been submitted for draft-ietf-ospf-auth-trailer-ospfv3-08.txt.
> http://www.ietf.org/internet-drafts/draft-ietf-ospf-auth-trailer-ospfv3-08.txt
> 
> 
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-ospf-auth-trailer-ospfv3-08
> 
> IETF Secretariat.
> 
> _______________________________________________
> OSPF mailing list
> OSPF <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ospf


Gmane