RFC 9493 on Subject Identifiers for Security Event Tokens

2023-12-06 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 9493 Title: Subject Identifiers for Security Event Tokens Author: A. Backman, Ed., M. Scurtescu, P. Jain Status: Standards Track

Protocol Action: 'Subject Identifiers for Security Event Tokens' to Proposed Standard (draft-ietf-secevent-subject-identifiers-18.txt)

2023-06-26 Thread The IESG
The IESG has approved the following document: - 'Subject Identifiers for Security Event Tokens' (draft-ietf-secevent-subject-identifiers-18.txt) as Proposed Standard This document is the product of the Security Events Working Group. The IESG contact persons are Paul Wouters and Roman Danyliw

Last Call: (Subject Identifiers for Security Event Tokens) to Proposed Standard

2022-10-27 Thread The IESG
The IESG has received a request from the Security Events WG (secevent) to consider the following document: - 'Subject Identifiers for Security Event Tokens' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send

Subject: NomCom 2021-2022: Composition of IETF Nominating Committee

2021-07-18 Thread NomCom Chair 2021
Please welcome NomCom 2021-2022! The challenge period has ended with no challenges following the update posted on July 8, 2021: https://datatracker.ietf.org/nomcom/ann/326222/ I'd like to thank the following individuals who have prioritized this service to the IETF Community. Voting Members:

RFC 8813 on Clarifications for Elliptic Curve Cryptography Subject Public Key Information

2020-08-12 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 8813 Title: Clarifications for Elliptic Curve Cryptography Subject Public Key Information Author: T. Ito, S. Turner Status

Protocol Action: 'Clarifications for Elliptic Curve Cryptogtaphy Subject Public Key Information' to Proposed Standard (draft-ietf-lamps-5480-ku-clarifications-03.txt)

2020-04-28 Thread The IESG
The IESG has approved the following document: - 'Clarifications for Elliptic Curve Cryptogtaphy Subject Public Key Information' (draft-ietf-lamps-5480-ku-clarifications-03.txt) as Proposed Standard This document is the product of the Limited Additional Mechanisms for PKIX and SMIME Working

Last Call: (Clarifications for Elliptic Curve Cryptogtaphy Subject Public Key Information) to Proposed Standard

2020-02-07 Thread The IESG
The IESG has received a request from the Limited Additional Mechanisms for PKIX and SMIME WG (lamps) to consider the following document: - 'Clarifications for Elliptic Curve Cryptogtaphy Subject Public Key Information' as Proposed Standard The IESG plans to make a decision in the next few

Subject: NomCom 2015-2016 Call for Volunteers

2015-05-19 Thread NomCom Chair 2015
DRAFT - points with XX need to be updated! Subject: NomCom 2015-2016 Call for Volunteers The IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. Ten voting members for the nomcom are selected in a verifiably random way from a pool of volunteers. The more

Protecting the disclosure of the identity (was: Loud humming is subject to cultural bias)

2013-08-01 Thread SM
Hi Andy, At 09:26 01-08-2013, Andy Bierman wrote: I meant that it is difficult to remain anonymous when the email to the WG has your email address in it. Agreed. Perhaps you can point me to the RFC 2026 text (or other RFC) that says something about protecting the disclosure of the identity

[no subject]

2013-07-30 Thread Aaron Yi DING
On 30/07/13 16:44, joel jaeggli wrote: On 7/30/13 4:40 PM, Arturo Servin wrote: Captchas? Recaptchas? Also, AFAIK WordPress has some good anti-spam add-ons. the obvious one is simply a requirement to use your ietf tools credientials to post. +1. the best current practice so far.

SUBJECT: UPDATED I2RS Working Group Interim Meeting April 22-23, 2013

2013-04-01 Thread IESG Secretary
A note from the I2RS Chairs regarding the Interim Meeting being held April 22-23, 2013 in Sunnyvale, CA: We've put up a registration page for the I2RS interim meeting at: http://i2rs-interim.eventbrite.com You must register in order to be able to attend. The cut off date for

Subject: New Non-WG Mailing List: coma -- Management of Constrained Networks and Devices

2012-05-16 Thread IETF Secretariat
A new IETF non-working group email list has been created. List address: c...@ietf.org Archive: http://www.ietf.org/mail-archive/web/coma/ To subscribe: https://www.ietf.org/mailman/listinfo/coma Purpose: This list is for the discussion related to the management of constrained networks

RFC 6495 on Subject Key Identifier (SKI) SEcure Neighbor Discovery (SEND) Name Type Fields

2012-02-03 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 6495 Title: Subject Key Identifier (SKI) SEcure Neighbor Discovery (SEND) Name Type Fields Author: R. Gagliano, S. Krishnan, A. Kukec

[no subject]

2011-12-04 Thread Weingarten, Yaacov (NSN - IL/Hod HaSharon)
Hi, Tom you wrote on 3 Dec: I would commend to you the e-mail that Russ posted here 30Nov2011 ... so claiming what is and is not part of MPLS-TP calls for some thought. I would suggest that you also read the following from the same e-mail from Russ to Malcolm Johnson: (2) I do not see

RE: Is G.8113.1 part of MPLS? (added subject)

2011-12-04 Thread Weingarten, Yaacov (NSN - IL/Hod HaSharon)
previous posting. Best regards, yaacov -Original Message- From: ext t.petch [mailto:daedu...@btconnect.com] Sent: Sunday, December 04, 2011 8:07 PM To: Weingarten, Yaacov (NSN - IL/Hod HaSharon); ietf@ietf.org; adr...@olddog.co.uk Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon) Subject: Re

Subject prefixes

2011-08-13 Thread Nick Hilliard
Can I humbly suggest that we create a separate working group to discuss whether there should be a subject_prefix for emails to ietf@ietf.org? This is an important issue for many people, and it would be unfortunate - nay, negligent - to make a decision on the matter without due discussion, debate

Re: Subject prefixes

2011-08-13 Thread Hector Santos
+1 and it should be begin with a reflection of what was then and what is now. Nick Hilliard wrote: Can I humbly suggest that we create a separate working group to discuss whether there should be a subject_prefix for emails to ietf@ietf.org? This is an important issue for many people, and it

[no subject]

2011-07-10 Thread Mark Andrews
...@muada.com 4e19c323.7020...@necom830.hpcl.titech.ac.jp Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE In-reply-to: Your message of Mon, 11 Jul 2011 00:20:03 +0900. 4e19c323.7020...@necom830.hpcl.titech.ac.jp In message 4e19c323.7020...@necom830.hpcl.titech.ac.jp, Masataka

[no subject]

2011-05-09 Thread myl@nd
-- Terre natale ! ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

[no subject]

2011-03-23 Thread myl@nd
-- Terre natale ! ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

[no subject]

2011-02-28 Thread dirt boy
I don't want to be a member thanks ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

[no subject]

2010-09-27 Thread The IESG
rfc-...@rfc-editor.org Subject: Re: Experimental RFC to be: draft-dzis-nwg-nttdm-04.txt The IESG has no problem with the publication of 'The Network Trouble Ticket Data Model' draft-dzis-nwg-nttdm-04.txt as an Experimental RFC. The IESG would also like the RFC-Editor to review the comments

Protocol Action: 'Subject Key Identifier (SKI) SEND Name Type fields.' to Proposed Standard

2010-06-04 Thread The IESG
The IESG has approved the following document: - 'Subject Key Identifier (SKI) SEND Name Type fields. ' draft-ietf-csi-send-name-type-registry-06.txt as a Proposed Standard This document is the product of the Cga Send maIntenance Working Group. The IESG contact persons are Ralph Droms

[no subject]

2010-04-14 Thread Jeyasekar Antony
http://docs.google.com/View?id=dfs6wf29_14jj9n62dh ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

[no subject]

2010-04-10 Thread Jeyasekar Antony
http://EsperanzaBlaszak2931.co.cc ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

[no subject]

2009-05-20 Thread jhanley
Dear Sir or Madam, Is there a working group on converging legacy protocol stacks and mapping legacy stacks addressing mechanisms into IPv6 addressing? For example, RFC 4291 4038 specifies that :::x.y.z.w represents IPv4 node x.y.z.w - is there a similar draft concept for specifying a Message

Subject: Call for IAOC Scribes

2009-04-09 Thread Bob Hinden
Since the days of the IASA transition team, Marshall Eubanks has acted as the scribe for the IAOC and IETF Trust. Since he was selected by the NOMCOM for membership on the IAOC he can no longer serve as scribe. The IAOC needs new scribes. Serving as the IAOC scribe is great way to learn

RFC 5480 on Elliptic Curve Cryptography Subject Public Key Information

2009-03-10 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5480 Title: Elliptic Curve Cryptography Subject Public Key Information Author: S. Turner, D. Brown, K. Yiu, R. Housley

[no subject]

2009-02-20 Thread Murray S. Kucherawy
On Thu, 19 Feb 2009 17:31:23 -0800 (PST), The IESG wrote: The IESG has received an appeal regarding the previously approved draft-kucherawy-sender-auth-header-20. The appeal text can be found here: http://www.ietf.org/IESG/APPEALS/appeal-otis-2009-02-16.txt [...] I am the author of the

[no subject]

2009-02-09 Thread Mauro Bieg
I urge you not to pass the 'TLS authorization extension' protocol as a standard unless the patent threat posed by RedPhone is removed entirely with a royalty-free license for all users. best regards, Mauro Bieg -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95

I Love this subject header! (was Re: Reject TLS!)

2009-02-09 Thread mshore
On 2/8/09 11:22 AM, Jeffrey Hankins jhank...@gmail.com wrote: Please stand up for software freedom and reject the TLS proposal until RedPhone Security issues a royalty-free patent for TLS. Thank you. And the content cracks me way the heck up, too. Otherwise this is really, really annoying.

Re: I Love this subject header! (was Re: Reject TLS!)

2009-02-09 Thread AJ Jaghori
Lol :) Its an interesting attempt, to say the least... On 2/9/09, mshore msh...@cisco.com wrote: On 2/8/09 11:22 AM, Jeffrey Hankins jhank...@gmail.com wrote: Please stand up for software freedom and reject the TLS proposal until RedPhone Security issues a royalty-free patent for TLS. Thank

Re: I Love this subject header! (was Re: Reject TLS!)

2009-02-09 Thread Randy Presuhn
; ietf@ietf.org; campai...@fsf.org Sent: Monday, February 09, 2009 3:41 PM Subject: Re: I Love this subject header! (was Re: Reject TLS!) Lol :) Its an interesting attempt, to say the least... On 2/9/09, mshore msh...@cisco.com wrote: On 2/8/09 11:22 AM, Jeffrey Hankins jhank

Last Call: draft-ietf-pkix-ecc-subpubkeyinfo (Elliptic Curve Cryptography Subject Public Key Information) to Proposed Standard

2008-11-25 Thread The IESG
The IESG has received a request from the Public-Key Infrastructure (X.509) WG (pkix) to consider the following document: - 'Elliptic Curve Cryptography Subject Public Key Information ' draft-ietf-pkix-ecc-subpubkeyinfo-10.txt as a Proposed Standard The IESG plans to make a decision

Subject: interim meeting on the topic of ipv4-ipv6 co-existence

2008-08-29 Thread IESG Secretary
An interim meeting will be organized on October 1 - 2 in Montreal, Canada to continue discussions about the IPv4 and IPv6 co-existence, NAT-PT replacement, and new tunneling or translation solutions to address needs in this space. This is a meeting that affects work happening in a number of WGs

[no subject]

2008-02-27 Thread The IESG
comments to the [EMAIL PROTECTED] mailing lists by 2008-03-14. Exceptionally, comments may be sent to [EMAIL PROTECTED] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-klensin

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-31 Thread Theodore Tso
On Mon, Dec 31, 2007 at 05:36:17AM +, Greg Skinner wrote: FWIW, I reread Russ Housley's comments on the outage, and understand it to be an experiment that is voluntary (but encouraged). Perhaps this needs to be stated differently (e.g. IPv6 experiment planned for IETF71 Plenary). I think

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned forIETF71 Plenary

2007-12-31 Thread Hallam-Baker, Phillip
AM Pacific Standard Time To: Greg Skinner Cc: Hallam-Baker, Phillip; IETF Discussion Subject:Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned forIETF71 Plenary On Mon, Dec 31, 2007 at 05:36:17AM +, Greg Skinner wrote: FWIW, I reread Russ Housley's comments

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned forIETF71 Plenary

2007-12-31 Thread Theodore Tso
To: Greg Skinner Cc: Hallam-Baker, Phillip; IETF Discussion Subject: Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned forIETF71 Plenary On Mon, Dec 31, 2007 at 05:36:17AM +, Greg Skinner wrote: FWIW, I reread Russ Housley's comments on the outage, and understand

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-31 Thread Joe Baptista
Theodore Tso wrote: I think the real issue here is the difference between what was originally stated (I think first by Marshall Rose in the Open Book) as the difference between the ISO, promulgating OSI, and the IETF, promulgating TCP/IP --- which was that ISO was populated primarily by

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-30 Thread Hallam-Baker, Phillip
from my GoodLink Wireless Handheld (www.good.com) -Original Message- From: Dave Crocker [mailto:[EMAIL PROTECTED] Sent: Friday, December 28, 2007 02:12 PM Pacific Standard Time To: Chris Lonvick Cc: ietf@ietf.org Subject:Re: Change the subject! RE: [IAOC] Re: IPv4

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-30 Thread Greg Skinner
Hallam-Baker, Phillip [EMAIL PROTECTED] wrote: It is a question of ambition. At sixteen I was interested in mastering the computer at its most fundamental level. I wrote arcade games in 6502 and Z80 assembler. Today the idea of booting linux on a laptop would not make my top ten, hundred or

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-30 Thread Hallam-Baker, Phillip
(www.good.com) -Original Message- From: Greg Skinner [mailto:[EMAIL PROTECTED] Sent: Sunday, December 30, 2007 01:44 PM Pacific Standard Time To: Hallam-Baker, Phillip Cc: IETF Discussion Subject:Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-30 Thread Greg Skinner
Pacific Standard Time To: Hallam-Baker, Phillip Cc: IETF Discussion Subject: Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary Hallam-Baker, Phillip [EMAIL PROTECTED] wrote: It is a question of ambition. At sixteen I was interested in mastering

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-28 Thread Chris Lonvick
Hi, Several people have written on this thread that they might not participate in this experiment because they either won't have an IPv6 stack or that they're unwilling to experiment with the network settings on their PCs. I'll suggest that those people can double their experimental fun in a

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-28 Thread Dave Crocker
Chris Lonvick wrote: Hi, Several people have written on this thread that they might not participate in this experiment because they either won't have an IPv6 stack or that they're unwilling to experiment with the network settings on their PCs. I'll suggest that those people can double

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF71 Plenary

2007-12-27 Thread Frank Ellermann
TS Glassey wrote: FWIW I have run into many people using down-rev laptop's for whom Microsoft's v6 implementation isn't ever going to be installed. See http://research.microsoft.com/msripv6/msripv6.htm - I found that via Jordi's http://www.ipv6-to-standard.org/ link. Apparently an

Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF 71 Plenary

2007-12-23 Thread Hallam-Baker, Phillip
9:46 PM To: [EMAIL PROTECTED] Cc: ietf@ietf.org Subject: Re: [IAOC] Re: IPv4 Outage Planned for IETF 71 Plenary [EMAIL PROTECTED] wrote: Russ Congrats. The ripples from this are and will be significant

Re: Change the subject! RE: [IAOC] Re: IPv4 Outage Planned for IETF 71 Plenary

2007-12-23 Thread JORDI PALET MARTINEZ
For products and services that support IPv6, take a look at: http://www.ipv6-to-standard.org/ Regards, Jordi De: Hallam-Baker, Phillip [EMAIL PROTECTED] Responder a: [EMAIL PROTECTED] Fecha: Sun, 23 Dec 2007 10:13:21 -0800 Para: ietf@ietf.org Conversación: Change the subject! RE: [IAOC] Re

(no subject)

2007-10-26 Thread rdroms
-Discussion discussion list ietf@ietf.org Content-Transfer-Encoding: 7bit From: Ralph Droms [EMAIL PROTECTED] Subject: Re: Lightening talks at the plenary Date: Tue, 23 Oct 2007 11:58:49 -0400 To: Hallam-Baker, Phillip [EMAIL PROTECTED] X-Mailer: Apple Mail (2.752.2) Return-Path: [EMAIL PROTECTED] X

(no subject)

2007-09-06 Thread rawad Melhem
I want to post ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: (no subject)

2007-09-06 Thread Dave Aronson
rawad Melhem wrote: I want to post Congratulations, you got your wish. Did you actually have anything to SAY? -- Dave Aronson Specialization is for insects. -Heinlein Work: http://www.davearonson.com/ Play: http://www.davearonson.net/ ___ Ietf

RFC 4985 on Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name

2007-08-29 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 4985 Title: Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name Author: S. Santesson

Protocol Action: 'Internet X.509 Public Key Infrastructure Subject Alternative Name for expression of service name' to Proposed Standard

2007-05-30 Thread The IESG
The IESG has approved the following document: - 'Internet X.509 Public Key Infrastructure Subject Alternative Name for expression of service name ' draft-ietf-pkix-srvsan-05.txt as a Proposed Standard This document is the product of the Public-Key Infrastructure (X.509) Working Group

A plea for subject line sanity (RE: DNS Choices: Was: [ietf-dkim] Re: Last Call: 'DomainKeys)

2006-12-07 Thread Harald Alvestrand
PLEASE it would be best for all, I think, if people who wish to rehash all the discussions from the ASRG mailing list take that discussion to the ASRG mailing list. But - failing that - could you PLEASE put the word SPAM in the subject line of your message, so that people who want

RE: A plea for subject line sanity (RE: DNS Choices: Was: [ietf-dkim] Re: Last Call: 'DomainKeys)

2006-12-07 Thread Hallam-Baker, Phillip
. But - failing that - could you PLEASE put the word SPAM in the subject Please don't do that. SPAM is subject line is used by large number of user filters tht post-process messages sent for example by SpamAssasin. Instead use Anti-Spam (note no capilization of spam) in the subject line

RFC 4683 on Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)

2006-10-05 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 4683 Title: Internet X.509 Public Key Infrastructure Subject Identification Method (SIM) Author: J. Park, J. Lee, H.. Lee, S. Park

Protocol Action: 'Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)' to Proposed Standard

2006-07-20 Thread The IESG
The IESG has approved the following document: - 'Internet X.509 Public Key Infrastructure Subject Identification Method (SIM) ' draft-ietf-pkix-sim-08.txt as a Proposed Standard This document is the product of the Public-Key Infrastructure (X.509) Working Group. The IESG contact persons

Last Call: 'Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)' to Proposed Standard

2006-03-06 Thread The IESG
The IESG has received a request from the Public-Key Infrastructure (X.509) WG to consider the following document: - 'Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)' draft-ietf-pkix-sim-07.txt as a Proposed Standard To distinguish among multiple individuals

Subject: IETF Last Call under RFC 3683 concerning Dean Anderson (reissued)

2005-10-18 Thread David Kessens
[NOTE: It has come to the attention of the IESG that the original Last Call message was posted to the IETF announcements mail list while RFC 3683 specifies that it should have been posted to the general IETF discussion list. To correct for this oversight, this Last Call message is reissued with a

Subject: IETF Last Call under RFC 3683 concerning Dean Anderson (reissued)

2005-10-14 Thread David Kessens
[NOTE: It has come to the attention of the IESG that the original Last Call message was posted to the IETF announcements mail list while RFC 3683 specifies that it should have been posted to the general IETF discussion list. To correct for this oversight, this Last Call message is reissued with a

(no subject)

2005-08-26 Thread Hallam-Baker, Phillip
From: Keith Moore [mailto:[EMAIL PROTECTED] I agree that getting authentication into the email protocols is a good thing, but TLS does not achieve much more than SPF/Sender-ID in that respect. DKIM is a much better platform. Not clear. As currently envisioned, DKIM doesn't

A Complaint to the IETF and IESG (was Re: Please change the Subject: when you change the subject [Re: Sarcarm and intimidation])

2005-08-02 Thread Dean Anderson
I haven't changed the subject. The correct subject is sarcasm and intimidation. I have just provided specific examples of sarcasm and intimidation that have happened while working on spam issues for the IETF. Those specific exmaples fall under the topic of the subject header. Your complaint about

Re: Please change the Subject: when you change the subject [Re: Sarcarm and intimidation]

2005-07-23 Thread shogunx
standards, and not letting lots of whining users who ccan't figure out how to operate a simple packet filter dictate our work. What I think is that if you change the subject, you should change the Subject:, so that people who might be interested in Sarcarm and intimidation but aren't interested

Please change the Subject: when you change the subject [Re: Sarcarm and intimidation]

2005-07-22 Thread Brian E Carpenter
... Does this mean that you think the IETF should disband the ASRG, drop all current I-D's relating to spam, and quit working on spam issues? What I think is that if you change the subject, you should change the Subject:, so that people who might be interested in Sarcarm and intimidation

RFC 4096 on Policy-Mandated Labels Such as Adv: in Email Subject Headers Considered Ineffective At Best

2005-05-27 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 4096 Title: Policy-Mandated Labels Such as Adv: in Email Subject Headers Considered Ineffective At Best Author(s): C. Malamud Status: Informational

Document Action: 'Policy-Mandated Labels Such as Adv: in Email Subject Headers Considered Ineffective At Best' to Informational RFC

2005-04-06 Thread The IESG
The IESG has approved the following document: - 'Policy-Mandated Labels Such as Adv: in Email Subject Headers Considered Ineffective At Best ' draft-malamud-subject-line-05.txt as an Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-25 Thread Carl Malamud
A very simple solution would be to write the documents in French :-) That would be illegal. ;) Carl ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-25 Thread Bob Braden
* * A very simple solution would be to write the documents in French :-) * * * That would be illegal. ;) * * Carl * Ah, but here is the clever bit. We don't CALL it French, we call it Freedom Language. Bob Braden ___ Ietf

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-25 Thread JFC (Jefsey) Morfin
At 11:30 25/02/2005, Carl Malamud wrote: A very simple solution would be to write the documents in French :-) That would be illegal. ;) This was a joke, but you make it an issue: illegal for who? ___ Ietf mailing list Ietf@ietf.org

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Carl Malamud
Merci bien pour votre suggestions ... JSPF (Je suis pas francais). :)) Regards, Carl [ Charset ISO-8859-1 unsupported, converting... ] This is an interesting proposal, however I would suggest that the grammatical mistakes relative to the french language and the cultural references be fixed.

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Joe Abley
of the solicitation class keyword. (Needless to say, the issue of how to define what classes of messages are subject to such a requirement and how to enforce it are beyond the scope of this discussion.) Joe ___ Ietf mailing list Ietf@ietf.org https://www1

RE: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Brian Rosen
I read the first draft of this document, and wondered: Does this propose to change IETF behavior on list management, so that the name of the list (usually same as working group) is not put in the Subject: using the feature of mailman that does this? When it was just a draft, it was just

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Carl Malamud
Hi Brian - I read the first draft of this document, and wondered: Does this propose to change IETF behavior on list management, so that the name of the list (usually same as working group) is not put in the Subject: using the feature of mailman that does this? That isn't the specific

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Randy Presuhn
Durand [EMAIL PROTECTED] Cc: ietf@ietf.org; iesg@ietf.org Sent: Thursday, February 24, 2005 7:00 AM Subject: Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC Merci bien pour votre suggestions ... JSPF (Je suis pas francais). :)) Regards, Carl

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Carl Malamud
Hi - http://www.ietf.org/ietf/1id-guidelines.txt says: Internet-Drafts must be in ASCII. No 8bit chars are currently allowed. If you need to include codepoints, a suggestion might be to use the unicode convention: U+, where X is a hexadecimal digit. So, for the quotes, if retaining

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Tony Hansen
The document does not discuss the type of mailing list subject labels that you're referring to. I'm arguing that a better title of the document would be Legislated Labels in Email Subject Headers Considered Ineffective At Best Tony Hansen [EMAIL PROTECTED] Carl Malamud

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread JFC (Jefsey) Morfin
At 00:15 25/02/2005, Carl Malamud wrote: http://trusted.resource.org/no-solicit/ has the xml source and the html rendition. In the xml, I use the proper utf-8, which shows up in full glory in the html. For the ascii version, I concur with Randy's opinion that it makes the most sense to sacrifice

Re: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-24 Thread Frank Ellermann
Carl Malamud wrote: my repeated apologies to any citizens of Freedonia as well Maybe you could mention that RfC 3834 with its [Auto] label is and was no problem, and it doesn't need any solicitation classes to work. But don't mention Re: unless you REally plan to REvive some endless threads,

Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

2005-02-23 Thread The IESG
The IESG has received a request from an individual submitter to consider the following document: - 'Labels in Subject Headers Considered Ineffective At Best ' draft-malamud-subject-line-02.txt as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final

Whilst we're on the subject of IPR (as usual)

2004-10-16 Thread Conroy, Lawrence (SMTP)
Hi Folks, In the process of submitting I-Ds to the new improved specs, I had reason to look at (and cut-and-paste from) the fine I-D guidelines document. I also tried out the XML2RFC 1.26 web service, and can attest that it adds no pain over and above that intrinsic in the use of XML (i.e.

(no subject)

2004-09-30 Thread deva
hi to all, I would like to ask if enyone knows how I can simulate the IEEE 802.11e using the OPNET simulator and if there is a new version that support it. I have the 8.0C... I would really appreciate any help... thanks in advance... Despina(deva) ___

[¯f¬rĵ§i](no subject)

2004-08-09 Thread clamav
PROTECTED] To: [EMAIL PROTECTED] Subj: (no subject) Date: Mon, 09 Aug 2004 18:20:17 -0500 Virus: Trojan.JS.RunMe Trojan.JS.RunMe ±zªº«H¥ó³Q°»´ú¥X§t¦³¯f¬r «H¥ó¤w³Q¥á±ó ¬ÛÃö¸ê®Æ¦p¤U: ±H¥óªÌ: [EMAIL PROTECTED] ¦¬¥óªÌ: [EMAIL PROTECTED] ¼ÐÃD: (no subject) ¤é´Á: Mon, 09 Aug 2004 18:20:17 -0500

Re: [¯f¬rĵ§i](no subject)

2004-08-09 Thread Valdis . Kletnieks
On Tue, 10 Aug 2004 06:40:30 +0800, [EMAIL PROTECTED] said: -- Warning: Message delivery wasn't performed. Reason: Our virus scanner detected very suspicious code in the attachment of a mail addressed to a user of our

Re: Mailing list identification, e.g., [IETF], in subject lines

2004-07-19 Thread Kai Henningsen
[EMAIL PROTECTED] (Harald Tveit Alvestrand) wrote on 15.07.04 in [EMAIL PROTECTED]: Short answer: No. Long answer: This item has been discussed to death once every 3 months on this very list. We have never found a consensus to add these tags. List-Id: IETF-Discussion ietf.ietf.org

[IETF] Mailing list identification, e.g., [IETF], in subject lines (was: RE: Names of standards-track RFCs )

2004-07-16 Thread JFC (Jefsey) Morfin
At 17:24 15/07/04, Harald Tveit Alvestrand wrote: This item has been discussed to death once every 3 months on this very list. We have never found a consensus to add these tags. It would be illusory to have everyone (consensus) accepting to be nice/polite to a few/many others and to conform to a

Mailing list identification, e.g., [IETF], in subject lines (was: RE: Names of standards-track RFCs )

2004-07-15 Thread John C Klensin
these email subject lines do not show the WG name... Request All to include a WG name in the subject line []s like [manet]. (which includes this email too!!) I would think IETF moderator should add that, but which WG?? Thanks, Harsh

Re: Mailing list identification, e.g., [IETF], in subject lines (was: RE: Names of standards-track RFCs )

2004-07-15 Thread Harald Tveit Alvestrand
Short answer: No. Long answer: This item has been discussed to death once every 3 months on this very list. We have never found a consensus to add these tags. Harald --On 15. juli 2004 10:35 -0400 John C Klensin [EMAIL PROTECTED] wrote: Hi. Since I'm the apparent offender...

Re: Mailing list identification, e.g., [IETF], in subject lines (was: RE: Names of standards-track RFCs )

2004-07-15 Thread David Frascone
Not to feed the troll, but, if I remember correctly, the overwhelming response is always: we don't need it. Procmail can filter fine without it. So, since there's no one vehemently opposed to it (that I can remember), why not just turn it on, to avoid the quarterly request? Not everyone uses

Re: Mailing list identification, e.g., [IETF], in subject lines (was: RE: Names of standards-track RFCs )

2004-07-15 Thread grenville armitage
David Frascone wrote: [..] So, since there's no one vehemently opposed to it (that I can remember), why not just turn it on, Finally we're a true Standards Organization. cheers, gja ___ Ietf mailing list [EMAIL PROTECTED]

[no subject]

2004-01-21 Thread Firat ARAS

[no subject]

2003-09-20 Thread Stanley Weilnau
As you probably have already noticed, email delievery from ietf.org has been reinstated. If you notice any issues, please email [EMAIL PROTECTED] Thank you, Stanley Weilnau

[no subject]

2003-09-07 Thread shogunx
Evening all, have we completely deprecated 's for A6's or is still considered bcp? Scott sleekfreak pirate broadcast world tour 2002-3 live from the pirate hideout http://sleekfreak.ath.cx:81/

[no subject]

2003-09-07 Thread Randy Bush
have we completely deprecated 's for A6's or is still considered bcp? we're keeping them both as we have moved ipv4 to experimental /sarcasm

[no subject]

2003-07-07 Thread massaly

please change the subject line

2003-03-25 Thread George Michaelson
Dean, please can you change the subject line. If you are going to complain to the IETF about process, I have absolutely no desire to be brought into it, and it certainly isn't part of anything I conciously wanted to initiate in my posting. cheers -George

[no subject]

2003-01-08 Thread Valdis . Kletnieks
On Wed, 08 Jan 2003 01:46:50 EST, Bill Cunningham [EMAIL PROTECTED] said: Who does the real IE work in the Internet world? Is it the IESG or IAB? That's what working groups are for. Seems like there's more arguing on this list than anything else. You haven't been here long, have you? ;)

[no subject]

2003-01-07 Thread Bill Cunningham
Who does the real IE work in the Internet world? Is it the IESG or IAB? Seems like there's more arguing on this list than anything else.

[no subject]

2002-12-24 Thread marco
Hi, I'm Marco from Italy. I'm querying my HP LANswitch by SNMP protocol to get relevant information about my LAN connections. I use snmpget, snmpgetnext and snmpwalk commands from a Linux RH 6.2 system. Is there a way to obtain a list of connected hosts to interfaces of the switch?? I

[no subject]

2002-10-01 Thread [EMAIL PROTECTED]
Hi, my name is Marco and I write from Italy. I have to develop a system to increase the security on my switched LAN. Switches forward all the broadcast traffic while unicast traffic is redirected only on the right segment... My idea is relying on broadcast traffic to map the hosts.to map

  1   2   >