Last Call: 'State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator' to Informational RFC

[The IESG]

The IESG has received a request from the Extensible Authentication Protocol WG 
to consider the following document:

- 'State Machines for Extensible Authentication Protocol (EAP) Peer and 
   Authenticator '
as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
[EMAIL PROTECTED] or [EMAIL PROTECTED] mailing lists by 2004-05-13.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-eap-statemachine-03.txt


___
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

WG Action: Conclusion of The Application Configuation Access Protocol (acap)

[The IESG]

The Application Configuation Access Protocol (ACAP) working group in the Application
Area has concluded. The group was initially chartered to develop
a general access mechanism for per-user and per-server structured lists of
information and to describe how to store specific structured lists, initially
application configuration options and address books. It produced a based
protocol (RFC 2244) and an anonymous SASL mechanism for use with
ACAP and other protocols (RFC 2245). While work related to
ACAP has proceeded intermittently since the completion of those RFCs,
the group does not currently have sufficient participation to continue.
Some of its existing documents may proceed as independent submissions,
if the energy of the authors allows; other work has been taken up in
new formats by other areas of the IETF.

The IESG contacts are Ted Hardie and Scott Hollenbeck.

The mailing list will be inactive.


___
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

Last Call: 'Domain-based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)' to Proposed Standard

[The IESG]

The IESG has received a request from an individual submitter to consider the 
following document:

- 'Domain-based Application Service Location Using SRV RRs and the Dynamic 
   Delegation Discovery Service (DDDS) '
as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
[EMAIL PROTECTED] or [EMAIL PROTECTED] mailing lists by 2004-05-27.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-daigle-snaptr-00.txt


___
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

Last Call: 'SASL in HTTP/1.1' to Proposed Standard

[The IESG]

The IESG has received a request from an individual submitter to consider the 
following document:

- 'SASL in HTTP/1.1 '
as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
[EMAIL PROTECTED] or [EMAIL PROTECTED] mailing lists by 2004-05-27.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-nystrom-http-sasl-11.txt


___
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

RFC 3746 on Forwarding and Control Element Separation (ForCES) Framework

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 3746

Title:  Forwarding and Control Element Separation (ForCES)
Framework
Author(s):  L. Yang, R. Dantu, T. Anderson, R. Gopal
Status: Informational
Date:   April 2004
Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Pages:  40
Characters: 98660
Updates/Obsoletes/SeeAlso:None

I-D Tag:draft-ietf-forces-framework-13.txt

URL:ftp://ftp.rfc-editor.org/in-notes/rfc3746.txt


This document defines the architectural framework for the ForCES
(Forwarding and Control Element Separation) network elements, and
identifies the associated entities and their interactions.

This document is a product of the Forwarding and Control Element
Separation Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3723 on Securing Block Storage Protocols over IP

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 3723

Title:  Securing Block Storage Protocols over IP
Author(s):  B. Aboba, J. Tseng, J. Walker, V. Rangan,
F. Travostino
Status: Standards Track
Date:   April 2004
Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Pages:  70
Characters: 171673
Updates/Obsoletes/SeeAlso:None

I-D Tag:draft-ietf-ips-security-19.txt

URL:ftp://ftp.rfc-editor.org/in-notes/rfc3723.txt


This document discusses how to secure block storage and storage
discovery protocols running over IP (Internet Protocol) using IPsec
and IKE (Internet Key Exchange).  Threat models and security protocols
are developed for iSCSI (Internet Protocol Small Computer System
Interface), iFCP (Internet Fibre Channel Storage Networking) and FCIP
(Fibre Channel over TCP/IP), as well as the iSNS (Internet Storage
Name Server) and SLPv2 (Service Location Protocol v2) discovery
protocols.  Performance issues and resource constraints are analyzed.

This document is a product of the IP Storage Working Group of the
IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3722 on String Profile for Internet Small Computer Systems Interface (iSCSI) Names

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 3722

Title:  String Profile for Internet Small Computer
Systems Interface (iSCSI) Names
Author(s):  M. Bakke
Status: Standards Track
Date:   April 2004
Mailbox:[EMAIL PROTECTED]
Pages:  8
Characters: 14702
Updates/Obsoletes/SeeAlso:None

I-D Tag:draft-ietf-ips-iscsi-string-prep-06.txt

URL:ftp://ftp.rfc-editor.org/in-notes/rfc3722.txt


This document describes how to prepare internationalized iSCSI names
to increase the likelihood that name input and comparison work
in ways that make sense for typical users throughout the world.

The Internet Small Computer Systems Interface (iSCSI) protocol
provides a way for hosts to access SCSI devices over an IP network.
The iSCSI end-points, called initiators and targets, each have a
globally-unique name that must be transcribable, as well as easily
compared.

This document is a product of the IP Storage Working Group of the
IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3720 on Internet Small Computer Systems Interface (iSCSI)

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 3720

Title:  Internet Small Computer Systems Interface (iSCSI)
Author(s):  J. Satran, K. Meth, C. Sapuntzakis,
M. Chadalapaka, E. Zeidner
Status: Standards Track
Date:   April 2004
Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Pages:  257
Characters: 578468
Updates/Obsoletes/SeeAlso:None

I-D Tag:draft-ietf-ips-iscsi-20.txt

URL:ftp://ftp.rfc-editor.org/in-notes/rfc3720.txt


This document describes a transport protocol for Internet Small
Computer Systems Interface (iSCSI) that works on top of TCP.  The
iSCSI protocol aims to be fully compliant with the standardized SCSI
architecture model.

SCSI is a popular family of protocols that enable systems to
communicate with I/O devices, especially storage devices.  SCSI
protocols are request/response application protocols with a common
standardized architecture model and basic command set, as well as
standardized command sets for different device classes (disks, tapes,
media-changers etc.).

As system interconnects move from the classical bus structure to a
network structure, SCSI has to be mapped to network transport
protocols.  IP networks now meet the performance requirements of
fast system interconnects and as such are good candidates to "carry"
SCSI.

This document is a product of the IP Storage Working Group of the
IETF. 

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3721 on Internet Small Computer Systems Interface (iSCSI) Naming and Discovery

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 3721

Title:  Internet Small Computer Systems Interface (iSCSI)
Naming and Discovery
Author(s):  M. Bakke, J. Hafner, J. Hufferd, K. Voruganti,
M. Krueger
Status: Informational
Date:   April 2004
Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Pages:  22
Characters: 47564
Updates/Obsoletes/SeeAlso:None

I-D Tag:draft-ietf-ips-iscsi-name-disc-10.txt

URL:ftp://ftp.rfc-editor.org/in-notes/rfc3721.txt


This document provides examples of the Internet Small Computer Systems
Interface (iSCSI; or SCSI over TCP) name construction and discussion
of discovery of iSCSI resources (targets) by iSCSI initiators.  This
document complements the iSCSI protocol document.  Flexibility is the
key guiding principle behind this document.  That is, an effort has
been made to satisfy the needs of both small isolated environments, as
well as large environments requiring secure/scalable solutions.

This document is a product of the IP Storage Working Group of the
IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Protocol Action: 'Negotiation of NAT-Traversal in the IKE' to Proposed Standard

[The IESG]

The IESG has approved the following document:

- 'Negotiation of NAT-Traversal in the IKE '
as a Proposed Standard

This document is the product of the IP Security Protocol Working Group. 

The IESG contact persons are Russ Housley and Steve Bellovin.

Technical Summary

  This document describes how to detect one or more network address
  translation devices (NATs) between IPsec hosts, and how to negotiate
  the use of UDP encapsulation of the IPsec packets through the NAT
  boxes in Internet Key Exchange (IKE) protocol.

Working Group Summary

  The IPsec Working Group came to consensus on this document.

Protocol Quality

  This document was reviewed by Russell Housley for the IESG.


___
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

Document Action: 'IETF Problem Resolution Process' to Informational RFC

[The IESG]

The IESG has approved the following document:

- 'IETF Problem Resolution Process '
as an Informational RFC

This document is the product of the Problem Statement Working Group. 

The IESG contact person is Harald Alvestrand.

Technical Summary

This document is being published mainly as a record of the 
deliberations of the Problem WG in regard to finding a process for resolving
the IETF's problems, and documents both things that were uncontroversial 
and things where the group failed to reach any consensus. It is being 
published for the historical record, not as a set of instructions for 
reforming the IETF.
 
Working Group Summary

The working group meeting in Minneapolis had rough consensus that the 
document should be published.
The tracker at  shows one Last Call 
comment.
 
Protocol Quality
 
The document has been reviewed for the IESG by Harald Alvestrand.

RFC Editor Note:

 Please delete sections 1.2, 1.3, and 1.4.
 Note also the following minor nits:

  Section 4.6: s/four major areas/five major areas/

  Section 5.1.1: s/non-tools- related/non-tools-related/

  Section 7: s/security- related/security-related/


___
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

RFC 3771 on The Lightweight Directory Access Protocol (LDAP) Intermediate Response Message

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 3771

Title:  The Lightweight Directory Access Protocol (LDAP)
Intermediate Response Message
Author(s):  R. Harrison, K. Zeilenga
Status: Standards Track
Date:   April 2004
Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED]
Pages:  8
Characters: 17114
Updates:2251

I-D Tag:draft-rharrison-ldap-intermediate-resp-01.txt

URL:ftp://ftp.rfc-editor.org/in-notes/rfc3771.txt


This document defines and describes the IntermediateResponse
message, a general mechanism for defining
single-request/multiple-response operations in Lightweight Directory
Access Protocol (LDAP).  The IntermediateResponse message is defined
in such a way that the protocol behavior of existing LDAP
operations is maintained.  This message is intended to be used in
conjunction with the LDAP ExtendedRequest and ExtendedResponse to
define new single-request/multiple-response operations or in
conjunction with a control when extending existing LDAP operations in
a way that requires them to return intermediate response information. 

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

To: [EMAIL PROTECTED]
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.