From owner-ietf-medfree@mail.imc.org Mon Oct 2 13:56:24 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11841 for ; Mon, 2 Oct 2000 13:56:24 -0400 (EDT) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA19779 for ietf-medfree-bks; Mon, 2 Oct 2000 10:31:12 -0700 (PDT) Received: from [165.227.249.17] (ip17.proper.com [165.227.249.17]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA19775 for ; Mon, 2 Oct 2000 10:31:11 -0700 (PDT) Mime-Version: 1.0 X-Sender: phoffman@mail.imc.org Message-Id: Date: Mon, 2 Oct 2000 10:34:58 -0700 To: ietf-medfree@imc.org From: Paul Hoffman / IMC Subject: Restricting posting to this list Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-medfree@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Well, the spam level has gotten out of control, so I have changed the list so that only people on the list can post to it. I'll monitor bounces and forward things as need be. If you are trying to post to the list but can't, feel free to contact me. --Paul Hoffman, Director --Internet Mail Consortium From owner-ietf-medfree@mail.imc.org Wed Oct 4 18:53:36 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA03481 for ; Wed, 4 Oct 2000 18:53:35 -0400 (EDT) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id PAA03376 for ietf-medfree-bks; Wed, 4 Oct 2000 15:38:44 -0700 (PDT) Received: from [165.227.249.17] (ip17.proper.com [165.227.249.17]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA03372 for ; Wed, 4 Oct 2000 15:38:43 -0700 (PDT) Mime-Version: 1.0 X-Sender: phoffman@mail.imc.org Message-Id: Date: Wed, 4 Oct 2000 15:42:39 -0700 To: ietf-medfree@imc.org From: Paul Hoffman / IMC Subject: RFC 2839 on Identifying Composite Media Features Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-medfree@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > >From owner-ietf-medfree Wed Oct 4 15:31:46 2000 >Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) > by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA03175 > for ; Wed, 4 Oct 2000 15:31:46 -0700 (PDT) >Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) > by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA14045; > Wed, 4 Oct 2000 15:35:43 -0700 (PDT) >Message-Id: <200010042235.PAA14045@boreas.isi.edu> >To: IETF-Announce: ; >Subject: RFC 2839 on Identifying Composite Media Features >Cc: rfc-ed@ISI.EDU, ietf-medfree@imc.org >Mime-Version: 1.0 >Content-Type: Multipart/Mixed; Boundary=NextPart >Date: Wed, 04 Oct 2000 15:35:43 -0700 >From: RFC Editor > > >--NextPart > > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2938 > > Title: Identifying Composite Media Features > Author(s): G. Klyne, L. Masinter > Status: Standards Track > Date: September 2000 > Mailbox: GK@ACM.ORG, LMM@acm.org > Pages: 18 > Characters: 34451 > Updates: 2533 > > I-D Tag: draft-ietf-conneg-feature-hash-05.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2938.txt > > >In RFC 2533, an expression format is presented for describing >media feature capabilities as a combination of simple media feature >tags. > >This document describes an abbreviated format for a composite media >feature set, based upon a hash of the feature expression describing >that composite. > >This document is a product of the Content Negotiation 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 IETF-REQUEST@IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info@RFC-EDITOR.ORG > 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 RFC-Manager@RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR@RFC-EDITOR.ORG. 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. > >--NextPart >Content-Type: Multipart/Alternative; Boundary="OtherAccess" > >--OtherAccess >Content-Type: Message/External-body; > access-type="mail-server"; > server="RFC-INFO@RFC-EDITOR.ORG" > >Content-Type: text/plain >Content-ID: <001004153316.RFC@RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2938 > >--OtherAccess >Content-Type: Message/External-body; > name="rfc2938.txt"; > site="ftp.isi.edu"; > access-type="anon-ftp"; > directory="in-notes" > >Content-Type: text/plain >Content-ID: <001004153316.RFC@RFC-EDITOR.ORG> > >--OtherAccess-- >--NextPart-- --Paul Hoffman, Director --Internet Mail Consortium From owner-ietf-medfree@mail.imc.org Thu Oct 5 12:53:16 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03079 for ; Thu, 5 Oct 2000 12:53:16 -0400 (EDT) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id JAA05525 for ietf-medfree-bks; Thu, 5 Oct 2000 09:39:32 -0700 (PDT) Received: from [165.227.249.17] (ip17.proper.com [165.227.249.17]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA05521 for ; Thu, 5 Oct 2000 09:39:30 -0700 (PDT) Mime-Version: 1.0 X-Sender: phoffman@mail.imc.org Message-Id: Date: Thu, 5 Oct 2000 09:43:32 -0700 To: ietf-medfree@imc.org From: Paul Hoffman / IMC Subject: RFC 2938 on Identifying Composite Media Features Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-medfree@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > >From owner-ietf-medfree Thu Oct 5 09:20:09 2000 >Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) > by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA05188 > for ; Thu, 5 Oct 2000 09:20:09 -0700 (PDT) >Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) > by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA14304; > Thu, 5 Oct 2000 09:24:04 -0700 (PDT) >Message-Id: <200010051624.JAA14304@boreas.isi.edu> >To: IETF-Announce: ; >Subject: RFC 2938 on Identifying Composite Media Features >Cc: rfc-ed@ISI.EDU, ietf-medfree@imc.org >Mime-Version: 1.0 >Content-Type: Multipart/Mixed; Boundary=NextPart >Date: Thu, 05 Oct 2000 09:24:04 -0700 >From: RFC Editor > > >--NextPart > > >A new Request for Comments is now available in online RFC libraries. > > > RFC 2938 > > Title: Identifying Composite Media Features > Author(s): G. Klyne, L. Masinter > Status: Standards Track > Date: September 2000 > Mailbox: GK@ACM.ORG, LMM@acm.org > Pages: 18 > Characters: 34451 > Updates: 2533 > > I-D Tag: draft-ietf-conneg-feature-hash-05.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2938.txt > > >In RFC 2533, an expression format is presented for describing >media feature capabilities as a combination of simple media feature >tags. > >This document describes an abbreviated format for a composite media >feature set, based upon a hash of the feature expression describing >that composite. > >This document is a product of the Content Negotiation 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 IETF-REQUEST@IETF.ORG. Requests to be >added to or deleted from the RFC-DIST distribution list should >be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > >Details on obtaining RFCs via FTP or EMAIL may be obtained by sending >an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body >help: ways_to_get_rfcs. For example: > > To: rfc-info@RFC-EDITOR.ORG > 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 RFC-Manager@RFC-EDITOR.ORG. Unless >specifically noted otherwise on the RFC itself, all RFCs are for >unlimited distribution.echo >Submissions for Requests for Comments should be sent to >RFC-EDITOR@RFC-EDITOR.ORG. 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. > >--NextPart >Content-Type: Multipart/Alternative; Boundary="OtherAccess" > >--OtherAccess >Content-Type: Message/External-body; > access-type="mail-server"; > server="RFC-INFO@RFC-EDITOR.ORG" > >Content-Type: text/plain >Content-ID: <001005091842.RFC@RFC-EDITOR.ORG> > >RETRIEVE: rfc >DOC-ID: rfc2938 > >--OtherAccess >Content-Type: Message/External-body; > name="rfc2938.txt"; > site="ftp.isi.edu"; > access-type="anon-ftp"; > directory="in-notes" > >Content-Type: text/plain >Content-ID: <001005091842.RFC@RFC-EDITOR.ORG> > >--OtherAccess-- >--NextPart-- --Paul Hoffman, Director --Internet Mail Consortium From owner-ietf-medfree@mail.imc.org Thu Oct 5 13:10:40 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03331 for ; Thu, 5 Oct 2000 13:10:40 -0400 (EDT) Received: by ns.secondary.com (8.9.3/8.9.3) id JAA05846 for ietf-medfree-bks; Thu, 5 Oct 2000 09:56:40 -0700 (PDT) Received: from nemo.corp.equinix.com (somehost-2.equinix.net [207.20.85.154]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA05841 for ; Thu, 5 Oct 2000 09:56:39 -0700 (PDT) From: hardie@equinix.com Received: (from hardie@localhost) by nemo.corp.equinix.com (8.9.3/8.9.3) id KAA05858; Thu, 5 Oct 2000 10:00:43 -0700 (PDT) Message-Id: <200010051700.KAA05858@nemo.corp.equinix.com> Subject: CONNEG has closed To: ietf-medfree@imc.org Date: Thu, 5 Oct 2000 10:00:42 -0700 (PDT) Cc: hardie@equinix.com (Ted Hardie) Reply-to: hardie@equinix.com X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-medfree@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit With the publication of the RFC on composite feature tags, the work items of the CONNEG working group have been completed. As a result, the IESG has just approved the closure of the working group. I would like to thank all of you for your participation in the working group. In particular, I would like to thank Graham Klyne for his tireless efforts as the working group's principal editor and Larry Masinter for his work in guiding the group. best regards, Ted Hardie Chair, CONNEG From owner-ietf-medfree@mail.imc.org Thu Oct 5 14:53:29 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04930 for ; Thu, 5 Oct 2000 14:53:29 -0400 (EDT) Received: by ns.secondary.com (8.9.3/8.9.3) id LAA08167 for ietf-medfree-bks; Thu, 5 Oct 2000 11:38:25 -0700 (PDT) Received: from [165.227.249.17] (ip17.proper.com [165.227.249.17]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA08161 for ; Thu, 5 Oct 2000 11:38:24 -0700 (PDT) Mime-Version: 1.0 X-Sender: phoffman@mail.imc.org Message-Id: In-Reply-To: <200010042235.PAA14045@boreas.isi.edu> References: <200010042235.PAA14045@boreas.isi.edu> Date: Thu, 5 Oct 2000 11:42:27 -0700 To: ietf-medfree@imc.org From: Paul Hoffman / IMC Subject: Re: RFC 2839 on Identifying Composite Media Features Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-medfree@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: And, as we close, let's be confused just one more time. The RFC is 283*8*, not 283*9*. The RFC Editor sent out two notices, one of which was incorrect. --Paul Hoffman, Director --Internet Mail Consortium From owner-ietf-medfree@mail.imc.org Thu Oct 5 14:56:38 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04979 for ; Thu, 5 Oct 2000 14:56:37 -0400 (EDT) Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id LAA08300 for ietf-medfree-bks; Thu, 5 Oct 2000 11:41:31 -0700 (PDT) Received: from [165.227.249.17] (ip17.proper.com [165.227.249.17]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA08296 for ; Thu, 5 Oct 2000 11:41:31 -0700 (PDT) Mime-Version: 1.0 X-Sender: phoffman@mail.imc.org Message-Id: Date: Thu, 5 Oct 2000 11:45:34 -0700 To: ietf-medfree@imc.org From: Paul Hoffman / IMC Subject: Re: RFC 2839 on Identifying Composite Media Features Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-medfree@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Even I can't get it straight. The RFC is 2938. That's two nine three eight. --Paul Hoffman, Director --Internet Mail Consortium