Re: ID Tracker State Update Notice: draft-ietf-syslog-transport-tls (fwd)
"tom.petch" <[email protected]>
| Newsgroups | gmane.ietf.syslog |
|---|---|
| Message-ID | <005f01c8ffdb$41c04720$0601a8c0@allison> |
I note that draft-hodges-server-ident-check to which we are invited to contribute and from which we are invited to copy is A) expird B) gives no indication of where it might be discussed; the only thing I am sure of is that it won't be the TLS list since they have refused to take on such work - sigh. Tom Petch ----- Original Message ----- From: "Chris Lonvick" <[email protected]> To: <[email protected]> Sent: Friday, August 15, 2008 4:05 PM Subject: [Syslog] ID Tracker State Update Notice: draft-ietf-syslog-transport-tls (fwd) > Hi Folks, > > ---------- Forwarded message ---------- > Date: Thu, 14 Aug 2008 11:49:05 -0700 (PDT) > From: The IESG <[email protected]> > Reply-To: [email protected] > To: [email protected] > Subject: ID Tracker State Update Notice: draft-ietf-syslog-transport-tls > > 'State Changes to IESG Evaluation::Revised ID Needed from IESG Evaluation by Cindy Morgan' > ID Tracker URL: https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14551&rf c_flag=0 > ---------- Forwarded message ---------- > > It looks like the telechat is over and we have some DISCUSSes and COMMENTs > to clear before the document becomes an RFC. The real meat is here: > https://datatracker.ietf.org/idtracker/ballot/2334/ > > We've already cleared the issue about a system port v. a registered port. > (The IESG is now debating the distinction between system and registered > ports but that's clearly outside of our discussion in this WG.) > > We can easily clear Tim Polk's COMMENT > https://datatracker.ietf.org/idtracker/draft-ietf-syslog-transport-tls/comment/8 4805/? > (I've reviewed and agree and would like a second on this.) > > Joe is looking at the other issues raised by Chris Newman. > https://datatracker.ietf.org/idtracker/draft-ietf-syslog-transport-tls/comment/8 4852/? > He'll likely have some answers early next week. Please provide input on > this to the list. > > Thanks, > Chris > _______________________________________________ > Syslog mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/syslog _______________________________________________ Syslog mailing list [email protected] https://www.ietf.org/mailman/listinfo/syslog