Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: IESG


Related Topics
45

In the News (Wed 30 Dec 09)

  
  RFC3710
The IESG is expected to ensure that the documents are of a sufficient quality for release as RFCs, that they describe their subject matter well, and that there are no outstanding engineering issues that should be addressed before publication.
RFC 3710 An IESG Charter February 2004 The IESG may decide that a document submitted for standards-track publication should instead be published as Experimental or Informational, or that a document submitted for Proposed standard should be published as a BCP, or vice versa.
The IESG may recommend that the document be published as-is, that it be reviewed by a working group, that the document be published with an IESG note indicating issues such as conflict with the IETF standards process, or may recommend that the document not be published.
www.unix.org.ua /rfc/rfc3710.html   (3165 words)

  
 Re: Should the IESG manage or not?
In the critical edge cases, that would permit the IESG to kill an idea by saying: (i) That idea/request/documentcannot go forward without technical review (ii) We refuse to authorize or manage such a review, therefore it will not occur and the idea or document is dead.
What I don't think the IESG is ethically permitted to do, even under the provisions of 3932, is say "it conflicts with work being done now in the IETF or that might be done in the future, so it can't be published, but we won't identify the work or facilitate a review".
That would be reasonable except for the fact that the IESG has appeared to send a clear message that the response to such an I-D would be the statement that it needed technical review and, presumably, that the IESG was not willing to try to seek or allocate resources to get it done.
www.mail-archive.com /ietf@ietf.org/msg21428.html   (2871 words)

  
 RFC 3932 - The IESG and RFC Editor Documents: Procedures. H. Alvestrand.
The IESG and the RFC Editor keep a running dialogue, in consultation with the IAB, on these other documents and their classification, but they are outside the scope of this memo.
RFC 3932 IESG and RFC Editor Documents: Procedures October 2004 RFC 3710 [4] section 5.2.2 describes the spring 2003 review process (even though the RFC was published in 2004); with the publication of this document, the procedure described in RFC 3710 is no longer relevant to documents submitted via the RFC Editor.
In the case of a possible conflict, the IESG may contact a WG or a WG chair for an outside opinion of whether publishing the document is harmful to the work of the WG and, in the case of a possible conflict with an IANA registration procedure, the IANA expert for that registry.
rfc.sunsite.dk /rfc/rfc3932.html   (1958 words)

  
 RFC 2727 - IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
The intent of this rule is to ensure that members of the IESG and IAB serve the number of years that best facilitates the review of one-half of the members each year.
It is consistent with this rule for the nominating committee to choose one or more of the currently open positions to which it may assign a term greater than 2 years in order to ensure the ideal application of this rule in the future.
Galvin Best Current Practice [Page 4] RFC 2727 IAB and IESG Selection February 2000 It is consistent with this rule for current nominating committee members who have served on prior nominating committees to advise the current committee on deliberations and results of the prior committee, as necessary and appropriate.
www.packetizer.com /rfc/rfc.cgi?num=2727   (4204 words)

  
 ACM Ubiquity - A Concise Guide to the Major Internet Bodies
GOVERNANCE: The IESG operates as an activity of ISOC and is responsible to it.
IESG decisions are subject to appeal to the IAB.
IESG decisions may be appealed to the IAB.
www.acm.org /ubiquity/views/v6i5_simoneli.html   (2740 words)

  
 IAB and IESG Recommendation for IETF Administrative Restructuring
The IAB and IESG are drafting a document that will describe the finer level of detail as to the respective roles and responsibilities of each of the players.
The IAB and IESG thus wish to acknowledge the collective contributions of members of the IETF community that have participated in the discussion of this topic.
The IESG and ISOC Board appointments will be expected to serve until the first IETF meeting of 2006, and the IAB appointment will be expected to serve until the first IETF meeting of 2007, assuming that the BCP is approved and the IAOC continues to have appointed members from these bodies.
www.alvestrand.no /ietf/adminrest/draft-iab-iesg-adminrest-rec-00.html   (13763 words)

  
 iesg-charter-03.txt
The IESG role in document review The IESG is expected to ensure that the documents are of a sufficient quality for release as RFCs, that they describe their subject matter well, and that there are no outstanding engineering issues that should be addressed before publication.
The IESG may decide that a document submitted for standards-track Alvestrand Expires September 30, 2003 [Page 9] Internet-Draft An IESG charter April 2003 publication should instead be published as Experimental or Informational, or that a document submitted for Proposed standard should be published as BCP, or vice versa.
Other IESG roles 7.1 Staff supervision The IETF Chair has primary responsibility for supervising the work of the IETF Secretariat, with the advice and consent of the IESG, the IAB Chair and the ISOC president.
ietfreport.isoc.org /idref/draft-iesg-charter   (3615 words)

  
 [saag] draft-iesg-tcpmd5app-00.txt
Alex, the terminology was always wrong, and I pointed that out to the IESG when the RFC was out for last call years ago.
But Jeff Schiller apparently didn't think the terminology error was worth fixing, and I doubt that the rest of the IESG was concerned back then.
So, in one sense there is no need to mention this in Steve's document, because it is just explaining why the IESG is making an exception for BGP, and LDP in the future.
bs.mit.edu /pipermail/saag/2004q2/000864.html   (812 words)

  
 Complaints Against The IESG and The RFC-Editor About Publication of RFC-2188 (ESRO)
The IESG should not be permitted to engage in censorship or delay of publication of work coming from outside of IETF because they just don't like it, because they don't understand it, because they think that it may be competing with IETF/IESG work or because they think that it may be bad for the Internet.
On April 3th we were told that The IESG had requested that the ESRO document not be published at this time and that they would be in contact with us after their meeting that coming week in Memphis.
IESG Note This protocol has not had the benefit of IETF Working Group review, but a cursory examination reveals several issues which may be significant issues for scalability.
www.esro.org /complaint-2188/one/main.html   (3969 words)

  
 IESG Working Group Actions, January - February 2001
And instead of offering a roundup of all IETF and IESG activities in each column, we'll be alternating between looking at the newest RFCs and covering all the other actions, from working group actions to the latest chatter on the IETF front.
The past month or so has seen an unusual number of working group actions by the IESG: nine new working groups announced since the start of the year (a tenth was announced December 2000), and six existing working groups' activities concluded during the same time.
According to a message from IESG member and IETF Chair Fred Baker, the traditional focus of the IETF has been "above the wire and below the application," meaning the IETF does not concern itself with how data is transmitted at the link layer or with how applications are specified.
www.enterprisenetworkingplanet.com /netsp/article.php/600411   (777 words)

  
 [No title]
However, the consensus view in the IESG was that the full impact of transition to "Simple CLNP" (or to any of the proposed approaches) had not yet been explored in sufficient detail to make a final recommendation possible at this time.
The IESG felt there needed to be an open and thorough evaluation of any proposed new routing and addressing architecture.
As the community has a chance to comment on these criteria, and as the IESG gets a better understanding of the issues relating to selection of a new routing and addressing architecture, this section may be revised and published in a separate document.
www.freesoft.org /CIE/RFC/Orig/rfc1380.txt   (5705 words)

  
 Cover Pages: IESG Announces Proposal for IETF Atom Publishing Format and Protocol Working Group.   (Site not responding. Last check: 2007-11-04)
Interoperability is a key concern for the design initiative; in order to ensure interoperability the WG will unambiguously identify required elements in formats, clearly nominate conformance levels for different types of software, and provide clear extensibility mechanisms and constraints upon them.
Key participants in the proposed IETF Atom WG are named in the draft IETF Charter available on the Atom Wiki, last modified on 2004-04-12 or later.
Comments: send comments on the proposal to the IESG by May 12, 2004.
xml.coverpages.org /ni2004-05-05-a.html   (1094 words)

  
 Internet Standards Organizations
IETF RFCs ETSI IRTF IESG IAB IANA ICANN W3C ITU
The IESG is directly responsible for the actions associated with entry into and movement along the Internet "standards track," including final approval of specifications as Internet Standards.
IESG Selection: The IAB appoints a new IETF chair and all other IESG candidates, from a list provided by the IETF nominating committee.
www.isoc.org /standards/orgs.shtml   (1010 words)

  
 IESG active projects (via CobWeb/3.1 planetlab1.netlab.uky.edu)   (Site not responding. Last check: 2007-11-04)
Ideally, the IESG should agree on what the most common causes for a DISCUSS are, and how to evaluate whether a particular issue is severe enough to warrant a DISCUSS.
Reason: IESG role in RFC Editor documents needs to be clear, and timing expectations need to be mutually agreed, and adhered to.
Reason: The IESG might need… some sort of a leadership position, perhaps a bit of an IESG (as opposed to IETF) chair, perhaps a second General AD, something so vague that we need to call it a “fleen” for now.
www.unreason.com.cob-web.org:8888 /jfp/iesg-projects   (1744 words)

  
 [No title]
The shift in the roles of the IAB and IESG that occurred as a result of the POISED work is to be documented.
The IESG chair has to be in this loop on this.
The IESG chair and the Standards Area Director will bring the issue before the IESG for discussion and take the resolution back to the parties.
mirror.switch.ch /ftp/doc/iesg/iesg.93-05-13   (1441 words)

  
 [No title]
The IESG agreed that a message be sent by the Chair to the IETF noting the IESG policy of not permitting the word "Requirement" in the title of informational RFCs submitted by Working Groups.
The IESG discussed the three informational RFC submissions received from the RFC Editors: Jeff Schiller is to contact the authors of the SSL protocol to discuss bring their work into the IETF.
The IESG decided that the topic of night WG meetings (8-10 pm) should be discussed during the Danvers Open Plenary slot.
www.merit.edu /internet/documents/iesg/iesg.95-01-26   (449 words)

  
 [No title]
This document was developed by the IPv6 Directorate, IAB and IESG, and is a recommendation from the IAB and IESG to the RIRs.
Address Delegation Recommendations The IESG and the IAB recommend the allocations for the boundary between the public and the private topology to follow those general rules: - /48 in the general case, except for very large subscribers.
IAB & IESG Informational [Page 7] RFC 3177 IAB/IESG Recommendations on IPv6 Addresses September 2001 The existing IPv4 Internet shows us that a network prefix which is independent of, and globally advertised to, all upstream providers permits the routing system to select a reasonably good path within the applicable policy.
www.rfc-editor.org /rfc/rfc3177.txt   (2816 words)

  
 RE: Complaints Against The IESG and The RFC-Editor About Publication o   (Site not responding. Last check: 2007-11-04)
> The IESG note about potential problems with the spec > were never substantiated (or even documented) in anyway -- this is > separate from lack of consultation with the author.
With respect to lack of substantiation of the IESG issues raised, you email in response to the comments provided by the IESG reads: ] Harald's observations are correct.
I not surprised that in the absence of clarity that the IESG added a note; my surprise is that everything wasn't held for the mystical revision of the specification which fixes all.
www.cctec.com /maillists/ietf/msg03749.html   (498 words)

  
 Internet Engineering Steering Group (iesg) Internet Drafts   (Site not responding. Last check: 2007-11-04)
RFC 2026 section 9.1 allows the IESG to grant a variance to the standard practices of the IETF.
This document explains why the IESG is considering doing so for the revised version of the BGP-4 specification, which refers normatively to RFC 2385, 'Protection of BGP Sessions via the TCP MD5 Signature Option'.
This document describes the IESG's procedures for handling documents submitted for RFC publication via the RFC Editor, subsequent to the changes proposed by the IESG at the Seoul IETF, March 2004.
www.potaroo.net /ietf/ids-wg-iesg.html   (199 words)

  
 IESG DARE Initiative   (Site not responding. Last check: 2007-11-04)
The IESG's new Datagram Abuse Resistance Education program has enlisted hundreds of participants to spread the good word about leaving behind the use of the repugnant User Datagram Protocol.
An IESG spokesman summarized the viewpoint by saying "Haven't we evolved as a people to the point where we can all agree that UDP is clearly detrimental and without any redeeming qualities?"
The IESG spokesman continued, "The sinful tempation of unfettered data transmission may be too great for those less informed.
www.inetpix.com /dare   (282 words)

  
 HTTP/1.1 Draft Standard Issues List (IESG Last Call Requested)
IESG last call of the specifications occurred in September 1998.
The issues here all relate to issues raised during and after the IESG last call period.
The following issues (all resolved before IESG last call was issued) have been moved to a separate page to keep them clearly separate from items raised during IESG last call.
www.w3.org /Protocols/HTTP/Issues   (890 words)

  
 Roxen Community: RFC 3710 An IESG charter (Informational)   (Site not responding. Last check: 2007-11-04)
In addition, members of the IETF Secretariat are subscribed to the mailing list and present in the IESG meetings as needed in order to serve as a support function.
The IESG will either approve or disapprove of the publication of the document on the standards track; no document can be published on the standards track without IESG approval.
The IESG may decide that a document submitted for standards-track publication should instead be published as Experimental or Informational, or that a document submitted for Proposed standard should be published as a BCP, or vice versa.
community.roxen.com /developers/idocs/rfc/rfc3710.html   (3156 words)

  
 [No title]
Submitted to IESG for PS: Router Alert - WG last call finished without comments today, so it will be sent to IESG now.
Submitted to IESG for Informational: The GSE analysis was at the IESG for a long time.
Their action has happened: there will be an announcement at the plenary tonight that the IANA has delegated the first allotments of sub-TLA space to the three registries.
playground.sun.com /ipv6/minutes/ipng-minutes-jul99.txt   (8664 words)

  
 RFC 1336 - Who's Who in the Internet Biographies of IAB, IESG and IRSG Members
He has been one of the initiators of the new RARE WG structure that was installed in May 1992, and that is now managed by the Rare Technical Committee, of which he is a member.
He joined the IESG in November 1991 as area co- director of the OSI Integration area.
As IESG Secretary, he is responsible for shepherding Internet standards track protocols through the standards process.
www.muonics.com /rfc/rfc1336.php   (10817 words)

  
 Iesg
...At that time the IESG discussed the issues being raised concerning the moderation of the.....That discussion reaffirmed previous IESG discussions that moderation of WG mailing list.....Bernstein therefore was left to address the issue of the appropriat
IESG defers discussion of the format document for two weeks
...So, it turns out that the IESG won't consider the Atom format document today, as we had.....Other IESG members may have other "discuss" votes later on, and those can be more.....And, a document can only be deferred once (that is, the IESG cannot use "d
www.plexxa.com /s/IESG   (219 words)

  
 Re: Should the IESG manage or not?
Someone could write an internet draft allocating the codepoint; if they believe that we should allocate the codepoint without technical review of the proposal, then they could contain few details on that draft about the proposal but instead reference the existing specification.
But, I also think the IESG's advice is at least partly accurate.
If people believe that the guidelines in RFC 2780 should encourage the IESG to assign options whenever the use is sufficiently specified and there is likely to be a significant deployment, then they could propose revising RFC 2780 with those requirements.
www.mail-archive.com /ietf@ietf.org/msg21429.html   (1568 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.