IANA and RFC office hours

ll make my interactions with the IANA and the RFC Editor more productive and more enjoyable for all concerned, and I strongly encourage the relevant organizations to continue the practice of IANA and RFC Editor office hours at future IETF meetings. Peter -- Peter Saint-Andre Jabber Software Found

Re: Last Call: 'The telnet URI Scheme' to Proposed Standard

> There are no normative references; There should be ... to the > URI scheme ( [rfc2396bis]) RFC 3986. Peter ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

WG+BOF chatrooms

nks! Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: WG+BOF chatrooms

On Wed, Mar 02, 2005 at 09:18:09PM -0800, Aaron Falk wrote: > Peter Saint-Andre wrote: > > FYI, I have just set up chatrooms at ietf.xmpp.org for all the BOFs > > which are currently listed on the IETF 62 agenda page: > > Peter- > > Many thanks! Can you confirm tha

BOF jabber rooms

Sam Hartman wrote: > Hi. The BOF jabber rooms seem not to exist yet. They do now. Sorry for the oversight. Peter smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: IETF Last Call for two IPR WG Dcouments

e Trustees of the IETF Trust. However, the outbound draft does not specify if the work of the Trustees shall be subject to review by the IPR WG, the IESG, the IAB, or the IETF community (e.g., in the form of an Internet-Draft) before it takes effect. Peter -- Peter Saint-Andre https://stpeter.im/ s

Re: IETF Last Call for two IPR WG Dcouments

Harald Tveit Alvestrand wrote: > > > --On Tuesday, March 25, 2008 21:30:54 -0600 Peter Saint-Andre > <[EMAIL PROTECTED]> wrote: > >> Russ Housley wrote: >>> During the Wednesday Plenary at IETF 71, I gave the IETF community a >>> "heads up&q

Re: IETF Last Call for two IPR WG Dcouments

s not complexity. Referencing the specific documents is > more restrictive than what the working group recommended. I don't see > why that would help anything. See above. Perhaps it would be more helpful to reference some specific licenses that would realize the stated intent? Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf

Re: IETF Last Call for two IPR WG Dcouments

Ray Pelletier wrote: > > Peter Saint-Andre wrote: > >> Joel M. Halpern wrote: >> >> >>> I do not understand the problem you want addressed. The way this is >>> worded, it doesn't matter what "open source" or "free software&quo

Re: IETF Last Call for two IPR WG Dcouments

ould be more productive to describe how members of the Internet community can provide input to the Trust regarding this issue (or any other, for that matter). It seems to me that the information at http://trustee.ietf.org/ does not describe the relevant processes, other than mentioning <mailt

Re: IETF Last Call for two IPR WG Dcouments

Ray Pelletier wrote: > The Trustees adopted the Non-Profit Open Software License 3.0 in > September 2007 as the license it would use for open sourcing software > done as work-for-hire and that contributed to it, at that time thinking > of code contributed by IETF volunteers. See: > http://truste

Re: IETF Last Call for two IPR WG Dcouments

te for RFC outbound licensing. Agreed. > Further information about NOSL 3.0 and related licenses, is at > www.rosenlaw.com/OSL3.0-explained.pdf. Reading. > For various reasons, AFL 3.0, also described in that paper, would perhaps be > a more appropriate outbound license for code

Re: IETF Last Call for two IPR WG Dcouments

censes > or, even better, pointing their lawyers at the potholes others have > hit would be very useful. But this draft is not the place to do it. And how do we provide suggestions to the Trustees in a formal manner? Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Descriptio

Re: IETF Last Call for two IPR WG Dcouments

Randy Presuhn wrote: > Hi - > >> From: "Peter Saint-Andre" <[EMAIL PROTECTED]> >> To: "Ted Hardie" <[EMAIL PROTECTED]> >> Cc: >> Sent: Sunday, March 30, 2008 6:03 PM >> Subject: Re: IETF Last Call for two IPR WG Dcouments &g

Re: FW: RFC 5241 on Naming Rights in IETF Protocols

Richard Shockey wrote: > Can this be extended to WG naming rights as well. :-) Hmm, those cost more. But the really expensive items are Areas. ;) Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signat

Re: Archives for closed WGs

Adrian Farrel wrote: Do we archive charters and complete millstones for closed WGs? Oh gosh, I hope we're not archiving all those WG millstones... /psa smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org http

Re: FW: IETF copying conditions

t they have more experience than I do with this particular attack, so for what it's worth I have decided to defer to them on this matter. Peter -- Peter Saint-Andre https://stpeter.im/ ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

Re: What Sort Of Jabber Server For IETF Conference?

long as your client supports RFC 3920/1 and XEP-0045 you will be able to get on the network and join the chatrooms. Peter -- Peter Saint-Andre https://stpeter.im/ ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

Re: What Sort Of Jabber Server For IETF Conference?

Athar Shiraz Siddiqui wrote: > On 11/11/08, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: >> As far as I know it uses the ejabberd codebase. > > Thanks! that will help! (I hope) > >> > How does one get an account on this jabber server? >> >> Yo

Re: IPR Questions Raised by Sam Hartman at the IETF 73 Plenary

Sam Hartman wrote: >> "Dave" == Dave CROCKER writes: > > Dave> Joel M. Halpern wrote: > >> Yes, having to get rights from folks is a pain. > > > Dave> When the person is not longer available, the effect is more > Dave> than discomfort. > > > Strictly speaking, that's not a

Re: 5378: A Worked Example

Wes Hardaker wrote: > I'm not a layer so I don't understand the rules. > I'm just somehow supposed to abide by the rules I don't understand. Maybe we don't have a layering problem, we have a lawyering problem. Repeat after me: I am not a layer! ___ Ietf

Re: [Ietf-honest] It's time for some new steps (was: [Welcome to the "Ietf-honest"mailing list])

em to take a few minutes to unsubscribe. Multiply by dozens or hundreds of people and you've wasted some significant man-hours. A simple invitation would have sufficed. Perhaps you might spend some quality time with RFC 1855? Peter -- Peter Saint-Andre https://stpeter.im/ ___

Re: Last Call: draft-ietf-enum-xmpp (IANA Registration for Enumservice 'XMPP') to Proposed Standard

raft-saintandre-rfc4622bis-00.txt&difftype=--hwdiff Peter -- Peter Saint-Andre XMPP Standards Foundation http://www.xmpp.org/xsf/people/stpeter.shtml smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https

Re: Updating the rules?

e, deciding on a technology without first defining the requirements can lead one astray. I agree that we need to "take the time to get security right"; but I'm afraid that the time to do so may be measured in years... Peter -- Peter Saint-Andre XMPP Standards Foundation http://www.x

Re: PKI is weakly secure

ve recommendations Mr. Masataka Ohta has regarding security, because all I've seen so far is "X, Y, and Z are useless"... Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: Do you want to have more meetings outside US ?

ss). I see a few potential benefits here: 1. Greater focus on rough consensus and running code. 2. Fewer bureaucracy headaches. 3. Reduced workload for our stressed-out IESG members. :) Just a thought... Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Des

Re: Charging I-Ds

way while > the i-d live in the automated part of the process? Expected result of charging per I-D: bigger I-Ds. /psa -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org http

Re: Charging I-Ds

Melinda Shore wrote: > On 7/31/07 1:01 PM, "Peter Saint-Andre" <[EMAIL PROTECTED]> wrote: >> Expected result of charging per I-D: bigger I-Ds. > > Library science research in the early 1980s > found that the number of authors was highly > correlated with ti

Re: Do you want to have more meetings outside US ?

Cyrus Daboo wrote: > Hi Peter, > > --On July 30, 2007 2:11:38 PM -0600 Peter Saint-Andre > <[EMAIL PROTECTED]> wrote: > >> Further, in-person meetings are so second-millennium. How about greater >> use of text chat, voice chat, and video chat for interim meetings

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

er fields in DomainKeys Identified Mail (DKIM) can help to mitigate against forging of the header (see [DKIMSIG]). *** (Where [DKIMSIG] is a reference to RFC 4871.) Thanks for the review. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

uld be to define a header field for including an im: URI and/or one for including a pres: URI. That seems fairly straightforward. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

e with this header field may provide useful input to that process. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

We could get around that by > adding a Sender: field on transmission but then it would go against RFC > 2822 Section 3.6.2. Hmm, yes, I think it would be best to avoid making that association. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signa

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

ds Foundation -- "a scribe for the text chat room that uses XMPP and XMPP-based extensions" or somesuch). I don't see a particularly good reason to fight over labelling, especially if this specification is Informational and the resulting header field is added to the provisional regis

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

Tony Finch wrote: > On Thu, 6 Sep 2007, Dave Crocker wrote: >> Peter Saint-Andre wrote: >> >>> Jabber is to XMPP as email is to SMTP+POP+IMAP. >> Well, I appreciate the effort, but no. >> IM is to XMPP as email is to SMTP et al. > > That would be prematur

Re: Required doc sections (Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt))

o IANA considerations. This draft has >> no ..."). > > I have already explained why I think this is a Very Bad Idea. Agreed. In my experience, the IANA does not want the I-D to contain a section entitled "IANA Considerations" if there are no actions required of the IANA.

Re: Required doc sections (Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt))

clude an "IANA Considerations" section since there were no actions required of the IANA. But perhaps that was a miscommunication. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: Required doc sections (Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt))

Peter Saint-Andre wrote: > Thomas Narten wrote: >>> Agreed. In my experience, the IANA does not want the I-D to contain a >>> section entitled "IANA Considerations" if there are no actions required >>> of the IANA. >> Your experience does not match

Re: Required doc sections (Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt))

Thomas Narten wrote: > Peter Saint-Andre <[EMAIL PROTECTED]> writes: > >> Thomas Narten wrote: >>>> Agreed. In my experience, the IANA does not want the I-D to contain a >>>> section entitled "IANA Considerations" if there are no actions req

Re: Last Call: draft-saintandre-jabberid (The Jabber-ID Header Field) to Proposed Standard

Frank Ellermann wrote: > Peter Saint-Andre wrote: > >> Eric Allman wrote: > >>> I don't see any reason why a new proposed standard should allow >>> obsolete syntax (specifically, obs-FWS in section 2). > >> Another reviewer pointed that out as w

Re: 2026, draft, full, etc.

only by advancing a technology to DS. If so, then perhaps it's OK that doing so is "a whole lot of work" as Eliot says. After all, advancing an I-D to RFC is a whole lot of work, too, but we generally consider that process to be beneficial. Maybe we need to more clearly enunciate th

Re: 2026, draft, full, etc.

e-xmpp-feature-set-00 Whether I can convince XMPP developers to submit implementation reports is another question. :) Perhaps more experiments along these lines are in order? Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature

Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt

Frank Ellermann wrote: > Peter Saint-Andre wrote on the message-headers list: > >> FYI > > Thanks. Frankly, I hate these drafts. Great! Honest feedback is appreciated and agreement is overrated. :) > 1 - why two drafts instead of one ? Because some people consider IM and

Re: [Ietf-message-headers] Re: Re:I-DAction:draft-saintandre-header-pres-00.txt

Frank Ellermann wrote: > Peter Saint-Andre wrote: > >>> 1 - why two drafts instead of one ? >> Because some people consider IM and presence to be fully separable >> features, which is why we have both the pres: and im: URI schemes > > Two schemes with a seman

Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt

SM wrote: > At 12:03 06-11-2007, Peter Saint-Andre wrote: >> > 1 - why two drafts instead of one ? >> >> Because some people consider IM and presence to be fully separable >> features, which is why we have both the pres: and im: URI schemes (as >> defined in R

Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt

SM wrote: > At 01:56 07-11-2007, Peter Saint-Andre wrote: >> I'm not sure what you mean by "feature". According to RFC 2779, IM and >> presence are separate domains of functionality, which is why there is an >> im: URI scheme and a pres: URI scheme. I don

Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt

SM wrote: > At 15:49 07-11-2007, Peter Saint-Andre wrote: >> But what is a Contact-ID? Any means by which you could contact me might >> be included in that category -- email, telephone, voicemail, fax, post >> office box, various IM addresses, IRC channels where I hang out, et

Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt

u're in favor of separate headers for XMPP URIs and SIP URIs, or does it mean that you would like to define a general-purpose "RTC ID" in which it would be allowable to plug in an XMPP URI, a SIP URI, or (presumably) other URIs for services or technologies (say, Skype) that meet some yet-to-be-defined criteria for real-time interaction? Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf

Re: IPv4 Outage Planned for IETF 71 Plenary

IETF Chair wrote: > How dark is the IPv6 Internet? Let's find out. This thread prompted me to ask one of my hosting providers about IPv6 support. I received the following long but entertaining reply, which I am forwarding on as anonymous feedback from the trenches. ** I always said that if

Re: ssl jabber?

On Mon, Jul 14, 2003 at 09:02:10AM +0200, Leif Johansson wrote: > It would be nice to be able to speak ssl to the conference server... True. Server-to-server TLS is part of the XMPP specs (where XMPP is an IETF adaptation of the Jabber protocol), but existing implementations have not yet been upda

Re: IETF jabber howto pointers please?

On Mon, Jul 14, 2003 at 06:32:37PM +1000, George Michaelson wrote: > Could somebody re-post a pointer to the canonical 'IETF jabber' howto please? http://www.jabber.org/ietf/chat.php I've just updated it to reflect the fact that hosting for the text conferencing service is in Vienna this time.

Re: IETF jabber howto pointers please?

PROTECTED]> if you would like to discuss this further. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php

i18n name badges

Proposals for making email addresses fully internationalized were a hot topic in Minneapolis. I'd like to suggest a more modest reform: fully internationalized IETF name badges. IETF 59 might be a fine venue for rolling those out... Peter -- Peter Saint-Andre Jabber Software Foundation

Re: Jabber at IETF-59

On Tue, Mar 02, 2004 at 12:58:46AM +0900, Yoshiro YONEYA wrote: > On Sun, 29 Feb 2004 21:43:02 +0100 Iljitsch van Beijnum <[EMAIL PROTECTED]> wrote: > > > On 29-feb-04, at 21:27, Doug Royer wrote: > > > > > He is looking for instructions. > > > > >> well, i'm in several rooms right now... they a

Re: text conferencing at the 55th IETF meeting in Atlanta

Admittedly the Jabber clients for MacOS are sub-optimal. Hopefully that situation will be remedied in time for San Francisco. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php On Mon, 18 Nov 2002, Patrik Fältström wrote: > I have tried b

Re: Barely literate minutes

x27;s minutes against the audio recording). I've done this in the past (full disclosure: not always) and it is a lot of work. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with undefined - http://ww

Re: Barely literate minutes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/28/12 2:45 PM, Dave Crocker wrote: > > > On 11/28/2012 1:36 PM, Peter Saint-Andre wrote: >> IMHO it is the chairs' responsibility to listen to the audio >> recording and produce minutes from that (or at least che

Re: I'm struggling with 2219 language again

c.) to avoid all possible confusion. Sure, it's a bit stilted, but we're not writing gorgeous prose here, we're writing technical specifications that need to be completely clear. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2

Re: Last Call: (Registration of Second-Level URI Namespaces Under "ietf") to Informational RFC

formational RFC I've reviewed this document and it appears to be a useful bit of housecleaning. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECA

Re: Last Call: (Experiences from Cross-Area Work at the IETF) to Informational RFC

rly clear. Unfortunately, I do not yet have actionable suggestions for improvement. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRHa

Re: Internet Draft Final Submission Cut-Off Today

t used to be 5 PM Pacific, now it's 24:00 UTC. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRLAbrAAoJEOoGpJErxa2pJCQQAK05V

Re: Time zones in IETF agenda

d Europe. > > It's a good place for meetings, and surprisingly easy to get to > from most of the world. I've said it before: just go back and forth between Iceland and Hawaii. Oh, and maybe Minneapolis for old-time's sake. ;-) Peter - -- Peter Saint-Andre https://stpete

Re: Appointment of a Transport Area Director

ems for the long-term health of Internet. If that leads to fewer working groups producing higher-quality output, so be it. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.en

Re: Internet Draft Final Submission Cut-Off Today

> neither happened) the draft would have been lost. Nothing is stopping you from using source control. :-) Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.

Re: Orlando time for human language draft discussion

I replied, sorry about the delay. It looks like Thursday lunch would work well. On 3/5/13 4:47 AM, Randall Gellens wrote: > Hi all, > > I created a Doodle poll to see if we can find a time in Orlando to meet > face to face. > > Doodle poll for time at Orlando to discuss open issues and moving >

Re: Mentoring

s like a capital idea. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRQdk8AAoJEOoGpJErxa2pPdsQAJUcCGS2AXr782bvWFS4V6gy synIw2Elc

Re: Mentoring

ur group, no? I mean the ones who you'd naturally ask to > take minutes, volunteer to edit the new document, etc. They would > also tend to be overbooked for such slots (and often they are WG > chairs themselves). Quite possibly. Peter - -- Peter Saint-Andre https://stpeter.im/ -

Re: Mentoring

a good mentor. > > So, please take mentoring as an activity for each one of us > interested in help new people get involved in the IETF and not just > pass the problem to our leaders. A big +1 to that! Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE--

Re: Less Corporate Diversity

to be a WG chair, but there is no way I could have been an area director until after our small company was acquired by Cisco. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbir

Re: On the tradition of I-D "Acknowledgements" sections

of Conditional Language of Requirements Levels 2012-07-31 Expired draft-baryun-roll-nap-00The Node Ability of Participation (NAP) 2012-08-01 Expired Peter -- Peter Saint-Andre https://stpeter.im/

Re: On the tradition of I-D "Acknowledgements" sections

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/25/13 9:35 AM, John C Klensin wrote: > > > --On Monday, March 25, 2013 09:05 -0600 Peter Saint-Andre > wrote: > >> On 3/25/13 1:11 AM, Loa Andersson wrote: >>> AB, >>> >>> I'v

Re: call for ideas: tail-heavy IETF process

On 5/1/13 10:39 AM, Carsten Bormann wrote: > On May 1, 2013, at 18:33, Michael Richardson > wrote: > >> we need to create a new category of document which amounts to >> "fully baked ID" > > Yes. (I'm not sure it's a category, it might just be a stage.) Isn't that Proposed Standard? Peter

Re: call for ideas: tail-heavy IETF process

On 5/1/13 11:27 AM, Paul Hoffman wrote: > On May 1, 2013, at 10:11 AM, Peter Saint-Andre > wrote: > >> On 5/1/13 10:39 AM, Carsten Bormann wrote: >>> On May 1, 2013, at 18:33, Michael Richardson >>> wrote: >>> >>>> we need to create a

Re: Language editing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/2/13 4:03 PM, Marc Petit-Huguenin wrote: > On 05/02/2013 02:40 PM, Yaron Sheffer wrote: >> As a non-native English speaker, but a language pedant >> nonetheless, I can empathize with people who put Discusses on >> badly written documents. > >> I

Re: call for ideas: tail-heavy IETF process

On 5/2/13 4:58 PM, Dave Crocker wrote: > On 5/2/2013 3:25 PM, Jari Arkko wrote: >> But the delay was really not my main concern. Primarily because I >> think other issues such as transparency to the working group or late >> surprises are more fundamental issues than mere timing. But also >> because

Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]

with clue in Area X to help WG Y in Area Z early and often with regard to specific issues that are often addressed in Area X). Unfortunately, this suffers from the same problem that too many WGs suffer from on their own: participant burnout. But I still think it's a good idea... Peter -- Peter Saint-Andre https://stpeter.im/

Re: IETF Meeting in South America

> Does this imply that, if we have a meeting in South America, I'll > need to wait another 10 years before I fly less than 24 hours to get > to an IETF meeting? Just in time for you to chair those WG sessions on HTTP/3.0... ;-) Peter -- Peter Saint-Andre https://stpeter.im/

Re: What do we mean when we standardize something?

shed. Otherwise I agree - if something's going > to be an IETF standard it needs to go through the IETF standards > development review and revision process, which is probably not what > the authors want. /me wonders if we need a separate series for informational documentation Pet

Re: Content-free Last Call comments

On 6/10/13 2:37 PM, Pete Resnick wrote: > I think we should stop with these one-line statements of support. +1 ;-) /psa

Re: Content-free Last Call comments

ause in good curmudgeonly style he needed something to grump at. In this instance, I suggest we just keep doing what we've always been doing. Peter - -- Peter Saint-Andre https://stpeter.im/ -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools -

Re: Content-free Last Call comments

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/12/13 12:44 PM, Peter Saint-Andre wrote: > On 6/12/13 12:38 PM, Alexey Melnikov wrote: >> On 12/06/2013 15:16, ned+i...@mauve.mrochek.com wrote: >>> Dave Cridland wrote: >>>> I strongly feel that positive

Re: IETF Diversity

nd WG chair roles) instead of pontificating at the mic. Peter -- Peter Saint-Andre https://stpeter.im/

Re: IETF Diversity

ou're getting busy from the ground up, instead of waiting for official action. > The issue was raised in the IETF plenary I would have expected mention > of a followup mailing list to be made here on the ietf discussion list. Fair enough. Peter -- Peter Saint-Andre https://stpeter.im/

Re: IETF Diversity

who talk and don't take action -- myself very much included. Peter -- Peter Saint-Andre https://stpeter.im/

Re: IETF Diversity

s really not a diversity issue, so if we're going to continue this thread I suggest that at the least we change the subject line. Peter -- Peter Saint-Andre https://stpeter.im/

Re: IETF Diversity

On 6/19/13 9:15 AM, Dave Crocker wrote: > On 6/19/2013 8:08 AM, Peter Saint-Andre wrote: >> On 6/19/13 8:32 AM, Dave Crocker wrote: >>> On 6/19/2013 5:35 AM, Dave Cridland wrote: >>>> Phillip Hallam-Baker wrote: >>>> There is a real problem with accoun

Re: IETF Diversity

On 6/19/13 9:22 AM, Melinda Shore wrote: > On 6/19/13 7:16 AM, Peter Saint-Andre wrote: >> Actually I see lots of structural problems -- I just happen to be of the >> mindset that working from the bottom up is the only sustainable model >> for change. > > Don't kno

Re: IETF Diversity

On 6/19/13 9:26 AM, Brian Haberman wrote: > On 6/19/13 11:08 AM, Peter Saint-Andre wrote: > >> >> My point, poorly expressed though it was, is that it's not productive >> for us all to wait from word on high before taking positive action. >> Members of the IESG

Re: IETF Diversity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/19/13 9:29 AM, Melinda Shore wrote: > On 6/19/13 7:26 AM, Peter Saint-Andre wrote: >> On 6/19/13 9:22 AM, Melinda Shore wrote: >>> Don't know about that one. In the US, at least, legal >>> mandates have typically

Re: IETF Diversity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/19/13 9:36 AM, Brian Haberman wrote: > On 6/19/13 11:31 AM, Peter Saint-Andre wrote: >> On 6/19/13 9:26 AM, Brian Haberman wrote: >>> On 6/19/13 11:08 AM, Peter Saint-Andre wrote: >>> >>>> >>>>

Re: IETF Diversity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/19/13 10:00 AM, Melinda Shore wrote: > On 6/19/13 7:56 AM, Peter Saint-Andre wrote: >> Why do you believe that my opinions are unexamined? I have been >> thinking and reading about social, cultural, and personal change >>

Re: IETF Diversity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/19/13 10:25 AM, Melinda Shore wrote: > On 6/19/13 8:12 AM, Peter Saint-Andre wrote: >> On 6/19/13 10:00 AM, Melinda Shore wrote: >>> On 6/19/13 7:56 AM, Peter Saint-Andre wrote: >>>> Why do you believe that my o

Re: IETF Diversity

biases exist. It's not at all clear that the existence of those > problems elsewhere corresponds to any actual problem within our > organization. > > That is NOT to say that we don't have a problem, only that making > conclusions based on unrelated data is bad science. On the other hand, every organization thinks it is special, and most aren't. :-) Peter -- Peter Saint-Andre https://stpeter.im/

Re: IETF Diversity

On 6/19/13 1:27 PM, Doug Barton wrote: > On 06/19/2013 12:14 PM, Peter Saint-Andre wrote: >> On 6/19/13 1:12 PM, Doug Barton wrote: >>> >>> We can point to all kinds of examples that are outside the IETF of where >>> various biases exist. It's not

Re: SHOULD and RECOMMENDED

e. Peter -- Peter Saint-Andre https://stpeter.im/

Re: SHOULD and RECOMMENDED

On 6/24/13 2:08 PM, Dave Crocker wrote: > On 6/24/2013 12:52 PM, Peter Saint-Andre wrote: >> I expect that the subtle differences between these words are lost on >> non-native speakers, and even most native speakers, of English. I'd be >> genuinely curious to hear t

Re: [IAB] RSOC Appointments

in IETF > experience, general requirements, etc. In the end, it is like we were > filling a job positions in an organization, the difference here is that > we are not receiving a salary. Agreed. Hiring without a job description is just silly... Peter -- Peter Saint-Andre https://stpeter.im/

Re: Make HTML and PDF more prominent, was: Re: Why the normative

On 3/19/10 3:33 PM, Martin Rex wrote: > Since we are writing RFCs in the _english_language_, so that they > can be consumed by the widest possible audience, _all_ text in them > ought to be written in the english language. Your statement bespeaks a certain degree of naïveté, à la those whose head

new URN discussion list

=subscribe Please note that the u...@ietf.org list is for discussion regarding the definition of URNs. We shall continue to use the urn-...@ietf.org list for review of Namespace Identifiers (NIDs). Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature

Re: Formal SPAM Compliant filed against Anderson...

On 5/3/10 11:25 AM, Joe Baptista wrote: > I think Dean does a good job of keeping the IETF honest. If only we could say the same thing about the IETF's effect on Dean. /psa smime.p7s Description: S/MIME Cryptographic Signature ___ Ietf mailing list

  1   2   3   4   >