<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.yam">
    <title>gmane.ietf.yam</title>
    <link>http://blog.gmane.org/gmane.ietf.yam</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/535"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/534"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/533"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/532"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/531"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/530"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/529"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/528"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/527"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/526"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/525"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/524"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/523"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/522"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/521"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/520"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/519"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/518"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/517"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.yam/516"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/535">
    <title>WG Action: Conclusion of Yet Another Mail (yam)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/535</link>
    <description>&lt;pre&gt;The Yet Another Mail (yam) working group in the Applications Area has 
concluded. The IESG contact persons are Pete Resnick and Peter Saint-Andre.

The mailing list will remain active.
&lt;/pre&gt;</description>
    <dc:creator>IESG Secretary</dc:creator>
    <dc:date>2011-11-28T17:57:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/534">
    <title>Re: (CFP) IEEE/IFIP International Workshop on Management of the Future Internet (ManFI 2012)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/534</link>
    <description>&lt;pre&gt;Hi Leonidas,

As one of the YAM mailing list moderators, I consider the content you 
posted as inappropriate as it is unrelated to the work described in 
the YAM working group charter.  Your messages to the mailing list 
will be moderated.

Regards,
S. Moonesamy

&lt;/pre&gt;</description>
    <dc:creator>S Moonesamy</dc:creator>
    <dc:date>2011-11-25T13:40:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/533">
    <title>(CFP) IEEE/IFIP International Workshop on Management of the Future Internet (ManFI 2012)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/533</link>
    <description>&lt;pre&gt;-----------------------------------------------------------------------------------------------------
    Please accept our apologies if you receive multiple copies of this CfP
-----------------------------------------------------------------------------------------------------


IEEE/IFIP International Workshop on Management of the Future Internet
(ManFI 2012)
==================================================================================
16 April 2012
Maui, Hawaii, USA
http://www.manfi.org


CALL FOR PAPERS
---------------
The Fourth IEEE/IFIP International Workshop on Management of the Future
Internet (ManFI 2012) will be held in conjunction with IEEE/IFIP NOMS 2012
in Maui, Hawaii, USA, from April 16-20, 2012. The workshop is sponsored by
the IEEE Communications Society (ComSoc) and supported by POSTECH ITCE,
Ghent University-IBBT, NEC, and Ericsson LM. The workshop is endorsed by
the Technical Committee on Network Operations and Management (CNOM).

It is widely agreed that, despite its many successes, the current Internet
also has a set of systemic problems, ranging from an upcoming shortage of
IP addresses to insufficient security. However, the lack of scalable and
agile manageability is arguably more important, as without management, it
is impossible to build systems that adapt the services and resources
offered in a context-dependent manner.

In either case (clean slate vs. evolution vs. revolution) we must consider
the manageability of the Future Internet from the beginning. Following the
success of the three previous editions of this workshop, held in
conjunction with IM 2009, NOMS 2010 and IM 2011, ManFI 2012 aims at
providing an international forum for researchers in these and similar
areas. ManFI 2012 will combine original full paper presentations with a
motivating keynote, quick hot topic presentations and a panel discussion
to thoroughly explore this challenging topic.


Topics of interest
------------------
Authors are invited to submit papers that fall into or are related to the
topic areas listed below:
- Architectural Issues
      * Advantages and disadvantages of revolutionary, evolutionary, and
other approaches to managing the Future Internet
      * Separation of data, control, and management planes
      * Design of architectural building blocks for managing the Future
Internet
      * Advances in measurement, management, security, accounting, mobility,
and other functions
      * Virtualization of resources and services
      * Dynamic composition of management and operational functionality
      * Mechanisms for managing interconnected computational infrastructures
(e.g. elastic clouds, federated clouds) in the Future Internet
      * Implications of social network success on the Future Internet
architecture
- Design and Implementation Issues
      * Abstractions for programmable network elements
      * Accommodating context-awareness in management
      * Applying  situation awareness to network management
      * Federation between administrative domains and support of all
constituencies
      * The role of models, ontologies, and other knowledge abstractions in
the Future Internet
      * Uncertainty and probabilistic approaches to management of the Future
Internet
      * Approaches for the organization of management data, data analytics
and visualization
      * Experience reports from Future Internet experimental facilities
set-up and results
- Economic Issues
      * Economic aspects driving the deployment of Future Internet  
management
technology
      * Economic opportunities and challenges for management technology
      * Experience reports from management in test beds


Paper submission
----------------
Paper submissions must present original, research or experiences.
Late-breaking advances and work-in-progress reports from ongoing research
are also encouraged. Only original papers that have not been published or
submitted for publication elsewhere can be submitted. Each submission must
be written in English, accompanied by a 75 to 200 word abstract that
clearly outlines the scope and contributions of the paper, and a list of
up to 5 key words. There is a length limitation of 6 pages (including
title, abstract, all figures, tables, and references) for regular
conference papers, and 4 pages for short papers. Submissions must be in
IEEE 2-column style. Papers exceeding these limits, multiple submissions,
and self-plagiarized papers will be rejected without further review.
Authors should submit their papers in PDF, postscript, or Word formats via
JEMS: (https://submissoes.sbc.org.br/).


Proceedings
-----------
Papers accepted for ManFI 2012 will be included in the conference
proceedings, IEEE Xplore, and EI Index. The IEEE reserves the right to
remove any paper from IEEE Xplore if the paper is not presented at the
workshop. Awards will be presented to the best paper and to the best
student paper at the workshop. Furthermore, we plan to work with a leading
journal, such as JNSM, TNSM and IJNM, to solicit extended versions of the
best papers of ManFI 2012 to be submitted for review.


Workshop Co-Chairs
------------------
- Prof. James Won-Ki Hong, POSTECH, Korea
- Prof. Filip De Turck, Ghent University - IBBT, Belgium
- Dr. Yoshiaki Kiriha, NEC, Japan
- Dr. Sven van der Meer, Ericsson LM, Ireland


Publicity Co-Chairs
-------------------
- Leonidas Lymberopoulos, National Technical University of Athens, Greece
- Cathryn Peoples, University of Ulster, UK


Important dates
---------------
- Abstract registration deadline: December 14, 2011
- Paper submission: December 20, 2011
- Notification of acceptance: January 31, 2012
- Final version of papers due: February 15, 2012
- Workshop date: April 16, 2012


For more information, please contact one of the Workshop Co-Chairs at
tpcchairs-0X+8w5kyo67sa1DXplZWQw&amp;lt; at &amp;gt;public.gmane.org
&lt;/pre&gt;</description>
    <dc:creator>Leonidas Lymberopoulos</dc:creator>
    <dc:date>2011-11-25T11:18:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/532">
    <title>Re: Last Call for YAM shutdown</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/532</link>
    <description>&lt;pre&gt;
Yes, just closing the loop.


I think this is OK. I'll be sure to ask the secretariat.


I think you mean "Dead". "Expired" is based entirely on the date of the 
draft, whereas "Dead" in the DataTracker means that it is no longer a 
watched item.

I will do so.

pr

&lt;/pre&gt;</description>
    <dc:creator>Pete Resnick</dc:creator>
    <dc:date>2011-11-22T12:07:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/531">
    <title>Re: Last Call for YAM shutdown</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/531</link>
    <description>&lt;pre&gt;Hi Pete,
At 22:03 21-11-2011, Pete Resnick wrote:

In a message posted on August 12 [1], the YAM WG co-chairs determined 
that there was consensus on shutting down the working group.

I suggest leaving the issues in the tracker open as they may be of 
use to people working on these RFCs in future.  Could you please 
change the status of draft-ietf-yam-5321bis-smtp-pre-evaluation-05 to Expired?

Regards,
S. Moonesamy
YAM WG co-chair

1. http://www.ietf.org/mail-archive/web/yam/current/msg00737.html 

&lt;/pre&gt;</description>
    <dc:creator>S Moonesamy</dc:creator>
    <dc:date>2011-11-22T07:45:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/530">
    <title>Last Call for YAM shutdown</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/530</link>
    <description>&lt;pre&gt;I plan to send the message in approximately 24 hours to shutdown YAM, 
leaving the mailing list open. Speak now or forever hold your peace.

pr

&lt;/pre&gt;</description>
    <dc:creator>Pete Resnick</dc:creator>
    <dc:date>2011-11-22T06:03:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/529">
    <title>Re: STD 72, RFC 6409 on Message Submission for Mail</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/529</link>
    <description>&lt;pre&gt;Yes, I wrote the message during that conversation of the plenary. :-)

On 11/16/2011 5:23 AM, Murray S. Kucherawy wrote:
&lt;/pre&gt;</description>
    <dc:creator>Tony Hansen</dc:creator>
    <dc:date>2011-11-16T16:19:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/528">
    <title>Re: STD 72, RFC 6409 on Message Submission for Mail</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/528</link>
    <description>&lt;pre&gt;


The last classic STD.

-Frank
&lt;/pre&gt;</description>
    <dc:creator>Frank Ellermann</dc:creator>
    <dc:date>2011-11-16T10:33:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/527">
    <title>Re: STD 72, RFC 6409 on Message Submission for Mail</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/527</link>
    <description>&lt;pre&gt;
That's funny.  Are you listening to the plenary?
&lt;/pre&gt;</description>
    <dc:creator>Murray S. Kucherawy</dc:creator>
    <dc:date>2011-11-16T10:23:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/526">
    <title>Re: STD 72, RFC 6409 on Message Submission for Mail</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/526</link>
    <description>&lt;pre&gt;With the publication of 6409, I believe that YAM's business is 
concluded. I expect to see the official wheels cranking through soon for 
us to shut down.

Thank you everyone for playing.

     Tony Hansen
     tony-60p5jsuXm+c&amp;lt; at &amp;gt;public.gmane.org

On 11/16/2011 4:35 AM, rfc-editor-i4YTrOVFbXmRpAAqCnN02g&amp;lt; at &amp;gt;public.gmane.org wrote:
&lt;/pre&gt;</description>
    <dc:creator>Tony Hansen</dc:creator>
    <dc:date>2011-11-16T10:18:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/525">
    <title>STD 72, RFC 6409 on Message Submission for Mail</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/525</link>
    <description>&lt;pre&gt;
A new Request for Comments is now available in online RFC libraries.

        STD 72        
        RFC 6409

        Title:      Message Submission for Mail 
        Author:     R. Gellens, J. Klensin
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    rg+ietf-zC7DfRvBq/JWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org, 
                    john-ietf-ompsCg6JJTw&amp;lt; at &amp;gt;public.gmane.org
        Pages:      20
        Characters: 40153
        Obsoletes:  RFC4409
        See Also:   STD0072

        I-D Tag:    draft-ietf-yam-rfc4409bis-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6409.txt

This memo splits message submission from message relay, allowing each
service to operate according to its own rules (for security, policy,
etc.), and specifies what actions are to be taken by a submission
server.

Message relay is unaffected, and continues to use SMTP over port 25.

When conforming to this document, message submission uses the
protocol specified here, normally over port 587.

This separation of function offers a number of benefits, including
the ability to apply specific security or policy requirements.  
[STANDARDS-TRACK]

This document is a product of the Yet Another Mail Working Group of the IETF.

This is now an Internet Standard.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor-i4YTrOVFbXnQdKpFsAHx7g&amp;lt; at &amp;gt;public.gmane.org  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


&lt;/pre&gt;</description>
    <dc:creator>rfc-editor-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2011-11-16T09:35:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/524">
    <title>(CFP) IEEE/IFIP International Workshop on Management of the Future Internet (ManFI 2012)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/524</link>
    <description>&lt;pre&gt;-----------------------------------------------------------------------------------------------------
  Please accept our apologies if you receive multiple copies of this CfP
-----------------------------------------------------------------------------------------------------


IEEE/IFIP International Workshop on Management of the Future Internet  
(ManFI 2012)
==================================================================================
16 April 2012
Maui, Hawaii, USA
http://www.manfi.org


CALL FOR PAPERS
---------------
The Fourth IEEE/IFIP International Workshop on Management of the Future  
Internet (ManFI 2012) will be held in conjunction with IEEE/IFIP NOMS 2012  
in Maui, Hawaii, USA, from April 16-20, 2012. The workshop is sponsored by  
the IEEE Communications Society (ComSoc) and supported by POSTECH ITCE,  
Ghent University-IBBT, NEC, and Ericsson LM. The workshop is endorsed by  
the Technical Committee on Network Operations and Management (CNOM).

It is widely agreed that, despite its many successes, the current Internet  
also has a set of systemic problems, ranging from an upcoming shortage of  
IP addresses to insufficient security. However, the lack of scalable and  
agile manageability is arguably more important, as without management, it  
is impossible to build systems that adapt the services and resources  
offered in a context-dependent manner.

In either case (clean slate vs. evolution vs. revolution) we must consider  
the manageability of the Future Internet from the beginning. Following the  
success of the three previous editions of this workshop, held in  
conjunction with IM 2009, NOMS 2010 and IM 2011, ManFI 2012 aims at  
providing an international forum for researchers in these and similar  
areas. ManFI 2012 will combine original full paper presentations with a  
motivating keynote, quick hot topic presentations and a panel discussion  
to thoroughly explore this challenging topic.


Topics of interest
------------------
Authors are invited to submit papers that fall into or are related to the  
topic areas listed below:
- Architectural Issues
    * Advantages and disadvantages of revolutionary, evolutionary, and  
other approaches to managing the Future Internet
    * Separation of data, control, and management planes
    * Design of architectural building blocks for managing the Future  
Internet
    * Advances in measurement, management, security, accounting, mobility,  
and other functions
    * Virtualization of resources and services
    * Dynamic composition of management and operational functionality
    * Mechanisms for managing interconnected computational infrastructures  
(e.g. elastic clouds, federated clouds) in the Future Internet
    * Implications of social network success on the Future Internet  
architecture
- Design and Implementation Issues
    * Abstractions for programmable network elements
    * Accommodating context-awareness in management
    * Applying  situation awareness to network management
    * Federation between administrative domains and support of all  
constituencies
    * The role of models, ontologies, and other knowledge abstractions in  
the Future Internet
    * Uncertainty and probabilistic approaches to management of the Future  
Internet
    * Approaches for the organization of management data, data analytics  
and visualization
    * Experience reports from Future Internet experimental facilities  
set-up and results
- Economic Issues
    * Economic aspects driving the deployment of Future Internet management  
technology
    * Economic opportunities and challenges for management technology
    * Experience reports from management in test beds


Paper submission
----------------
Paper submissions must present original, research or experiences.  
Late-breaking advances and work-in-progress reports from ongoing research  
are also encouraged. Only original papers that have not been published or  
submitted for publication elsewhere can be submitted. Each submission must  
be written in English, accompanied by a 75 to 200 word abstract that  
clearly outlines the scope and contributions of the paper, and a list of  
up to 5 key words. There is a length limitation of 6 pages (including  
title, abstract, all figures, tables, and references) for regular  
conference papers, and 4 pages for short papers. Submissions must be in  
IEEE 2-column style. Papers exceeding these limits, multiple submissions,  
and self-plagiarized papers will be rejected without further review.  
Authors should submit their papers in PDF, postscript, or Word formats via  
JEMS: (https://submissoes.sbc.org.br/).


Proceedings
-----------
Papers accepted for ManFI 2012 will be included in the conference  
proceedings, IEEE Xplore, and EI Index. The IEEE reserves the right to  
remove any paper from IEEE Xplore if the paper is not presented at the  
workshop. Awards will be presented to the best paper and to the best  
student paper at the workshop. Furthermore, we plan to work with a leading  
journal, such as JNSM, TNSM and IJNM, to solicit extended versions of the  
best papers of ManFI 2012 to be submitted for review.


Workshop Co-Chairs
------------------
- Prof. James Won-Ki Hong, POSTECH, Korea
- Prof. Filip De Turck, Ghent University - IBBT, Belgium
- Dr. Yoshiaki Kiriha, NEC, Japan
- Dr. Sven van der Meer, Ericsson LM, Ireland


Publicity Co-Chairs
-------------------
- Leonidas Lymberopoulos, National Technical University of Athens, Greece
- Cathryn Peoples, University of Ulster, UK


Important dates
---------------
- Abstract registration deadline: December 14, 2011
- Paper submission: December 20, 2011
- Notification of acceptance: January 31, 2012
- Final version of papers due: February 15, 2012
- Workshop date: April 16, 2012


For more information, please contact one of the Workshop Co-Chairs at  
tpcchairs-0X+8w5kyo67sa1DXplZWQw&amp;lt; at &amp;gt;public.gmane.org
&lt;/pre&gt;</description>
    <dc:creator>Leonidas Lymberopoulos</dc:creator>
    <dc:date>2011-11-07T11:49:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/523">
    <title>Protocol Action: 'Message Submission for Mail' to FullStandard(draft-ietf-yam-rfc4409bis-03.txt)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/523</link>
    <description>&lt;pre&gt;The IESG has approved the following document:
- 'Message Submission for Mail'
  (draft-ietf-yam-rfc4409bis-03.txt) as a Full Standard

This document is the product of the Yet Another Mail Working Group.

The IESG contact persons are Pete Resnick and Peter Saint-Andre.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-yam-rfc4409bis/




Technical Summary

This document splits message submission from message relay, allowing each
service to operate according to its own rules (for security, policy, etc.)
and specifies what actions are to be taken by a submission server.

Working Group Summary

The YAM WG adopted a two-step approach to move this document to Full Standard.
The first step was a pre-evaluation of the existing specification to identify
changes and non-changes. The second step was to incorporate the changes into
the document and ensure that any implementation that conforms to the Draft
Standard version of the specification remains compliant with this document.
There was no controversy. There is consensus to move the specification to
Full Standard.

Document Quality

The document has a high degree of technical maturity. In the five years since
publication of the Draft Standard and 13 years since publication as Proposed
Standard, the specification has become an integral part of all professional
SMTP software products and is widely supported in Internet Mail operations.
Chris Newman suggested adding Section 5.3 applying shorter timeouts.
John Klensin wrote the text in Section 6.5 which discusses about adjusting
character encodings.

Personnel

S. Moonesamy is the Document Shepherd for this document. Pete Resnick is the
Responsible Area Director.
&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2011-09-06T14:39:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/522">
    <title>I-D Action: draft-ietf-yam-rfc4409bis-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/522</link>
    <description>&lt;pre&gt;A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Yet Another Mail Working Group of the IETF.

Title           : Message Submission for Mail
Author(s)       : Randall Gellens
                          John C Klensin
Filename        : draft-ietf-yam-rfc4409bis-03.txt
Pages           : 22
Date            : 2011-09-02

   This memo splits message submission from message relay, allowing each
   service to operate according to its own rules (for security, policy,
   etc.), and specifies what actions are to be taken by a submission
   server.

   Message relay is unaffected, and continues to use SMTP over port 25.

   When conforming to this document, message submission uses the
   protocol specified here, normally over port 587.

   This separation of function offers a number of benefits, including
   the ability to apply specific security or policy requirements.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-yam-rfc4409bis-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-yam-rfc4409bis-03.txt
&lt;/pre&gt;</description>
    <dc:creator>internet-drafts-EgrivxUAwEY&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2011-09-02T18:37:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/521">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02:(with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/521</link>
    <description>&lt;pre&gt;The text in the fourth paragraph of Section 8 of 
draft-ietf-yam-rfc4409bis-02 will be replaced with the following text:

     "Message modification can affect the validity of an existing message
      signature, such as by DKIM [DKIM], PGP [RFC4880], S/MIME [RFC5751]
      and can render the  signature invalid.  This, in turn, can affect
      message handling by later receivers, such as filtering engines that
      consider the presence or absence of a valid signature."

Regards,
S. Moonesamy, Tony Hansen
co-chairs, YAM

&lt;/pre&gt;</description>
    <dc:creator>S Moonesamy</dc:creator>
    <dc:date>2011-08-27T04:24:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/520">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02: (with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/520</link>
    <description>&lt;pre&gt;
I like the above text. :-)

Regards,
-sm 

&lt;/pre&gt;</description>
    <dc:creator>SM</dc:creator>
    <dc:date>2011-08-27T04:39:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/519">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02: (with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/519</link>
    <description>&lt;pre&gt;And everybody said together: "there be dragons". :-) Consequently, I 
think we should go with the following text:

Incantation modifications can affect the efficacy of spells, such as 
those introduced by the presence of various species of dragons, both 
big, small and purple, some of which can even render the spell useless. 
This in turn can affect secondary applications of the spells, such as 
those applied by certain minor mages who cannot handle the violet spectrum.

Sorry, I was feeling a bit of whimsey. I think it's all this prepping 
for hurricanes.

     Tony Hansen

On 8/26/2011 1:45 PM, Murray S. Kucherawy wrote:
&lt;/pre&gt;</description>
    <dc:creator>Tony Hansen</dc:creator>
    <dc:date>2011-08-27T04:00:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/518">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02: (with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/518</link>
    <description>&lt;pre&gt;
You beat me to it.

+1 to Barry's last post.

-MSK
&lt;/pre&gt;</description>
    <dc:creator>Murray S. Kucherawy</dc:creator>
    <dc:date>2011-08-26T17:45:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/517">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02:(with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/517</link>
    <description>&lt;pre&gt;
Same here, better than my current text.

R's,
John
&lt;/pre&gt;</description>
    <dc:creator>John Levine</dc:creator>
    <dc:date>2011-08-26T16:27:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/516">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02: (with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/516</link>
    <description>&lt;pre&gt;Barry said exactly what I was going to say here. +1 on all points, including
the preference for Dave's text.

Ned











&lt;/pre&gt;</description>
    <dc:creator>Ned Freed</dc:creator>
    <dc:date>2011-08-26T16:08:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.yam/515">
    <title>Re: Russ Housley's Discuss on draft-ietf-yam-rfc4409bis-02: (with DISCUSS)</title>
    <link>http://permalink.gmane.org/gmane.ietf.yam/515</link>
    <description>&lt;pre&gt;
I'll repeat that my very strong preference is what's above.


Well, it certainly *is* a substantive comment, but put it in
perspective.  "Dave thinks Russ is wrong," is not enough to have Russ
clear his DISCUSS ballot.  "The working group considered Russ's
comments, and its consensus is that he's wrong," may well be a part of
convincing him to clear.

I don't think it's a secondary argument, to be held back because the
"primary" argument is more compelling.  I think it's an important
adjunct to *any* argument, to say that the WG as a whole is behind
what's being said.


I'm not sure what "this last issue" is, because the last thing you
mention is a comment by John that doesn't raise an issue.  But
assuming that's what you want comments on:


I think a primary goal is to make implementors aware of the fact that
modifications can affect digital signatures, in general terms.  Dave's
text does that, and gives references to some of the most common
signature mechanisms that MSAs are likely to encounter.  So I repeat
that I think Dave's text is appropriate, and also appropriately
concise.  I think John's text is too much, and doesn't add enough
extra benefit.

That paragraph was, indeed, meant as a simple "there be dragons"
statement, and I strongly support leaving it simple.

Barry
&lt;/pre&gt;</description>
    <dc:creator>Barry Leiba</dc:creator>
    <dc:date>2011-08-26T13:07:42</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.yam">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.yam</link>
  </textinput>
</rdf:RDF>
