Archive of ietf-usefor, by thread

• Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, (continued)
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Kai Henningsen
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Frank Ellermann
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Frank Ellermann
  • NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Russ Allbery
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Henry Spencer
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Ruud H.G. van Tol
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Henry Spencer
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Russ Allbery
  • Meta (was: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues), Frank Ellermann
  • Re: Meta (was: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues), Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Frank Ellermann
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Richard Clayton
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: Meta (was: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues), Ruud H.G. van Tol
  • Our web site, Charles Lindsey
  • Re: Our web site, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Charles Lindsey
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Frank Ellermann
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Bruce Lilly
  • Re: NEW: Path field delimiters and components; also #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Frank Ellermann
  • #1047: Path field delimiters and components, Harald Tveit Alvestrand
  • Re: #1047: Path field delimiters and components, Charles Lindsey
  • Re: #1047: Path field delimiters and components, Bruce Lilly
  • Re: #1047: Path field delimiters and components, Charles Lindsey
  • Re: #1047: Path field delimiters and components, Russ Allbery
  • Re: #1047: Path field delimiters and components, Bruce Lilly
  • Re: #1047: Path field delimiters and components, Charles Lindsey
  • Re: #1047: Path field delimiters and components, Frank Ellermann
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Charles Lindsey
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Charles Lindsey
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Charles Lindsey
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Charles Lindsey
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Frank Ellermann
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Henry Spencer
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Frank Ellermann
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Frank Ellermann
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Russ Allbery
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Frank Ellermann
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Ned Freed
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Charles Lindsey
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Charles Lindsey
    • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, also #1030 backward compatibility and handling incompatibilities, Bruce Lilly
  • Re: #1003 USEFOR 3.1.3 - Resolution of msg-id issues, Kai Henningsen
• #1002 USEFOR 6. References - propose to accept and leave to editor to write, Harald Tveit Alvestrand
  • Re: #1002 USEFOR 6. References - propose to accept and leave to editor to write, Frank Ellermann
• Re: Newsgroup names #1021, John Stanley
• Re: Admin: Please watch your language, John Stanley
• Re: Newsgroup names #1021 (was: #1008 USEFOR 1.5 References: Final text on "followup"), John Stanley
  • Re: Newsgroup names #1021 (was: #1008 USEFOR 1.5 References: Final text on "followup"), Harald Tveit Alvestrand
• Friday - Ticket status, Harald Tveit Alvestrand
• Admin: Posters this week, Harald Tveit Alvestrand
  • <Possible follow-ups>
  • Admin: Posters this week, Harald Tveit Alvestrand
  • Admin: Posters this week, Harald Tveit Alvestrand
• #1008 USEFOR 1.5 References: Final text on "followup", Harald Tveit Alvestrand
  • Newsgroup names #1021 (was: #1008 USEFOR 1.5 References: Final text on "followup"), Frank Ellermann
    • Re: Newsgroup names #1021 (was: #1008 USEFOR 1.5 References: Final text on "followup"), Harald Tveit Alvestrand
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Frank Ellermann
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Henry Spencer
      • Re: Newsgroup names #1021, Ruud H.G. van Tol
      • Re: Newsgroup names #1021, Harald Tveit Alvestrand
      • Re: Newsgroup names #1021, Frank Ellermann
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Henry Spencer
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Seth Breidbart
      • Re: Newsgroup names #1021, Henry Spencer
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Henry Spencer
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Frank Ellermann
      • Re: Newsgroup names #1021, Frank Ellermann
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
      • Re: Newsgroup names #1021, Ruud H.G. van Tol
      • Re: Newsgroup names #1021, Charles Lindsey
      • Re: Newsgroup names #1021, Russ Allbery
  • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
    • Guaranteed MUSTard (was: #1008 USEFOR 1.5 References: Final text on "followup"), Frank Ellermann
      • Re: Guaranteed MUSTard (was: #1008 USEFOR 1.5 References: Final text on "followup"), Charles Lindsey
      • Re: Guaranteed MUSTard, Frank Ellermann
      • Re: Guaranteed MUSTard, Charles Lindsey
      • Re: Guaranteed MUSTard, Harald Tveit Alvestrand
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Forrest J. Cavalier III
      • References semantics (Re: #1008 USEFOR 1.5 References: Final text on "followup"), Harald Tveit Alvestrand
      • Re: References semantics (Re: #1008 USEFOR 1.5 References: Final text on "followup"), Forrest J. Cavalier III
      • Ticket system mechanics (Re: References semantics (Re: #1008 USEFOR 1.5 References: Final text on "followup")), Harald Tveit Alvestrand
      • Tickets for USEPRO (Re: Ticket system mechanics), Harald Tveit Alvestrand
      • NEW: USEFOR 5. MIME boundary security considerations, Frank Ellermann
      • Re: NEW: USEFOR 5. MIME boundary security considerations, Bruce Lilly
      • Re: NEW: USEFOR 5. MIME boundary security considerations, Frank Ellermann
      • #1046: USEFOR 5. MIME boundary security considerations, Harald Tveit Alvestrand
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Richard Clayton
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Richard Clayton
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • #1003 affects USEPRO followups (was: #1008 USEFOR 1.5 References: Final text on "followup"), Frank Ellermann
      • Re: #1003 affects USEPRO followups (was: #1008 USEFOR 1.5 References: Final text on "followup"), Charles Lindsey
      • Semantic & Header content (Re: #1008 USEFOR 1.5 References: Final text on "followup"), Harald Tveit Alvestrand
      • Re: Semantic & Header content, Frank Ellermann
      • Re: Semantic & Header content (Re: #1008 USEFOR 1.5 References: Final text on "followup"), Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Richard Clayton
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Henry Spencer
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Seth Breidbart
      • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
  • <Possible follow-ups>
  • #1008 USEFOR 1.5 References: Final text on "followup", John Stanley
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Henry Spencer
  • Re: #1008 USEFOR 1.5 References: Final text on "followup", John Stanley
  • Re: #1008 USEFOR 1.5 References: Final text on "followup", John Stanley
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
  • Re: #1008 USEFOR 1.5 References: Final text on "followup", John Stanley
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
  • Re: #1008 USEFOR 1.5 References: Final text on "followup", John Stanley
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
  • Re: #1008 USEFOR 1.5 References: Final text on "followup", John Stanley
    • Re: #1008 USEFOR 1.5 References: Final text on "followup", Charles Lindsey
• #1029: USEFOR 3.2.2 References: Should comments be a MUST NOT?, Harald Tveit Alvestrand
• #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Harald Tveit Alvestrand
  • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Henry Spencer
    • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Charles Lindsey
  • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Bruce Lilly
    • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Russ Allbery
      • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Frank Ellermann
      • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Russ Allbery
      • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Graham Drabble
      • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Russ Allbery
      • Re: #1028 USEFOR 3.1.2: What zones should be on the MUST accept list?, Graham Drabble
• #1022 Summary: Should dot be permitted in phrases?, Harald Tveit Alvestrand
  • Re: #1022 Summary: Should dot be permitted in phrases?, Russ Allbery
  • Re: #1022 Summary: Should dot be permitted in phrases?, Bruce Lilly
    • Re: #1022 Summary: Should dot be permitted in phrases?, Harald Tveit Alvestrand
      • Re: #1022 Summary: Should dot be permitted in phrases?, Bruce Lilly
      • Re: #1022 Summary: Should dot be permitted in phrases?, Harald Tveit Alvestrand
      • standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Bruce Lilly
      • Re: standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Forrest J. Cavalier III
      • #1031 Re: standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Harald Tveit Alvestrand
      • Re: #1031 Re: standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Forrest J. Cavalier III
      • Re: #1031 Re: standard terminology and text, Russ Allbery
      • Re: #1031 Re: standard terminology and text, Harald Tveit Alvestrand
      • Re: #1031 Re: standard terminology and text, Henry Spencer
      • Re: #1031 Re: standard terminology and text, Forrest J. Cavalier III
      • Re: #1031 Re: standard terminology and text, Bruce Lilly
      • Re: #1031 Re: standard terminology and text, Henry Spencer
      • Re: #1031 Re: standard terminology and text, Frank Ellermann
      • Re: #1031 Re: standard terminology and text, Charles Lindsey
      • Re: #1031 Re: standard terminology and text, Frank Ellermann
      • Re: #1031 Re: standard terminology and text, Bruce Lilly
      • Re: #1031 Re: standard terminology and text, Frank Ellermann
      • Re: #1031 Re: standard terminology and text, Charles Lindsey
      • Re: #1031 Re: standard terminology and text, Harald Tveit Alvestrand
      • Re: #1031 Re: standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Harald Tveit Alvestrand
      • Re: #1031 Re: standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Bruce Lilly
      • Admin: Please watch your language, Harald Tveit Alvestrand
      • Re: Admin: Please watch your language, Forrest J. Cavalier III
      • Re: Admin: Please watch your language, Eivind Tagseth
      • Re: Admin: Please watch your language, Bruce Lilly
      • [off list] Re: Admin: Please watch your language, Frank Ellermann
      • OT, Frank Ellermann
      • Re: Admin: Please watch your language, Bruce Lilly
      • Re: Admin: Please watch your language, Russ Allbery
      • Re: #1031 Re: standard terminology and text (was #1022 Summary: Should dot be permitted in phrases?), Forrest J. Cavalier III
      • backward compatibility and handling incompatibilities (was #1022 Summary: Should dot be permitted in phrases?), Bruce Lilly
      • Re: backward compatibility and handling incompatibilities (was #1022 Summary: Should dot be permitted in phrases?), Henry Spencer
      • Re: #1031 backward compatibility and handling incompatibilities, Charles Lindsey
      • Re: #1031 backward compatibility and handling incompatibilities, Bruce Lilly
      • Re: #1031 backward compatibility and handling incompatibilities, Richard Clayton
      • Re: #1031 backward compatibility and handling incompatibilities, Frank Ellermann
      • Re: backward compatibility and handling incompatibilities (was #1022 Summary: Should dot be permitted in phrases?), Forrest J. Cavalier III
      • #1030 Re: backward compatibility and handling incompatibilities (was #1022 Summary: Should dot be permitted in phrases?), Harald Tveit Alvestrand
      • Re: #1030 Re: backward compatibility and handling incompatibilities (was #1022 Summary: Should dot be permitted in phrases?), Charles Lindsey
      • Re: #1022 Summary: Should dot be permitted in phrases?, Bruce Lilly
      • LTRU questions (was: #1022 Summary: Should dot be permitted in phrases?), Frank Ellermann
      • NEW USEPRO 7.9 gateway (was: LTRU questions), Frank Ellermann
      • Re: NEW USEPRO 7.9 gateway (was: LTRU questions), Charles Lindsey
      • Re: #1022 Summary: Should dot be permitted in phrases?, Charles Lindsey
      • Re: #1022 Summary: Should dot be permitted in phrases?, Forrest J. Cavalier III
      • Re: #1022 Summary: Should dot be permitted in phrases?, Harald Tveit Alvestrand
      • Re: #1022 Summary: Should dot be permitted in phrases?, Russ Allbery
      • Re: #1022 Summary: Should dot be permitted in phrases?, Forrest J. Cavalier III
      • documenting new fields (was #1022 Summary: Should dot be permitted in phrases?), Bruce Lilly
      • Re: documenting new fields (was #1022 Summary: Should dot be permitted in phrases?), Forrest J. Cavalier III
      • #1032 documenting new fields (was #1022 Summary: Should dot be permitted in phrases?), Harald Tveit Alvestrand
    • Re: #1022 Summary: Should dot be permitted in phrases?, Charles Lindsey
      • Re: #1022 Summary: Should dot be permitted in phrases?, Harald Tveit Alvestrand
      • Re: #1022 Summary: Should dot be permitted in phrases?, Charles Lindsey
• #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Harald Tveit Alvestrand
  • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Charles Lindsey
    • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Bruce Lilly
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Charles Lindsey
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Russ Allbery
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Charles Lindsey
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Russ Allbery
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Frank Ellermann
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Russ Allbery
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Frank Ellermann
      • OT: "UT", Bruce Lilly
      • Re: OT: "UT", Russ Allbery
      • Re: OT: "UT", Charles Lindsey
      • Re: OT: "UT", Richard Clayton
      • Re: OT: "UT", Seth Breidbart
      • Re: OT: "UT", Russ Allbery
      • OT: EST (was: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?), Frank Ellermann
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Bruce Lilly
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Charles Lindsey
      • Date-time yet again, Bruce Lilly
      • Re: Date-time yet again, Charles Lindsey
      • Re: Date-time yet again, Bruce Lilly
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Russ Allbery
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Charles Lindsey
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Russ Allbery
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Frank Ellermann
      • Re: #1022: USEFOR 2.1 obs-phrase: Should dot be permitted in phrases?, Russ Allbery
• #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", Ruud H.G. van Tol
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Seth Breidbart
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Russ Allbery
      • CFWS in References header, Harald Tveit Alvestrand
      • Re: CFWS in References header, Forrest J. Cavalier III
      • Re: CFWS in References header, Harald Tveit Alvestrand
      • Re: CFWS in References header, Charles Lindsey
      • Re: CFWS in References header, Russ Allbery
      • Re: CFWS in References header, Charles Lindsey
      • Re: CFWS in References header, Russ Allbery
      • INN implementation clarifications, Bruce Lilly
      • Re: INN implementation clarifications, Russ Allbery
      • Re: INN implementation clarifications, Frank Ellermann
      • IPv6 literals in Path (Re: INN implementation clarifications), Harald Tveit Alvestrand
      • Re: IPv6 literals in Path (Re: INN implementation clarifications), Russ Allbery
      • Re: INN implementation clarifications, Bruce Lilly
      • Re: INN implementation clarifications, Russ Allbery
      • Newsgroups folding test (was CFWS in References header), Charles Lindsey
      • Re: Newsgroups folding test, Frank Ellermann
      • Re: Newsgroups folding test, Russ Allbery
      • Re: Newsgroups folding test, Harald Tveit Alvestrand
      • Re: Newsgroups folding test, Charles Lindsey
      • Re: Newsgroups folding test (was CFWS in References header), Richard Clayton
      • Re: CFWS in References header, Bruce Lilly
      • Re: CFWS in References header, Charles Lindsey
      • Re: CFWS in References header, Bruce Lilly
      • Re: CFWS in References header, Charles Lindsey
      • Re: CFWS in References header, Bruce Lilly
      • Re: CFWS in References header, Russ Allbery
      • Forward compatibility (Re: CFWS in References header), Harald Tveit Alvestrand
      • Re: Forward compatibility (Re: CFWS in References header), Charles Lindsey
      • Re: Forward compatibility (Re: CFWS in References header), Russ Allbery
      • Re: Forward compatibility (Re: CFWS in References header), Charles Lindsey
      • Re: Forward compatibility (Re: CFWS in References header), Russ Allbery
      • Re: Forward compatibility (Re: CFWS in References header), Charles Lindsey
      • Re: Forward compatibility (Re: CFWS in References header), Russ Allbery
      • Re: Forward compatibility (Re: CFWS in References header), Charles Lindsey
      • Re: Forward compatibility (Re: CFWS in References header), Harald Tveit Alvestrand
      • Re: Forward compatibility (Re: CFWS in References header), Kai Henningsen
      • Re: Forward compatibility, Frank Ellermann
      • Re: Forward compatibility, Charles Lindsey
      • Re: Forward compatibility, Eivind Tagseth
      • OT: 78 (was Forward compatibility), Charles Lindsey
      • Re: OT: 78 (was Forward compatibility), Eivind Tagseth
      • OT: 78 (was: Forward compatibility), Frank Ellermann
      • Re: OT: 78 (was: Forward compatibility), Charles Lindsey
      • Re: OT: 78, Frank Ellermann
      • Re: OT: 78, Charles Lindsey
      • Re: Forward compatibility (Re: CFWS in References header), Graham Drabble
      • Re: Forward compatibility (Re: CFWS in References header), Richard Clayton
      • Re: Forward compatibility (Re: CFWS in References header), Charles Lindsey
      • Re: CFWS in References header, Russ Allbery
      • Re: CFWS in References header, Bruce Lilly
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • You critiqued USEPRO....Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: You critiqued USEPRO....Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Russ Allbery
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Frank Ellermann
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Henry Spencer
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Eivind Tagseth
      • Re: #1008 USEFOR 1.5: Suggested language on "followup", Charles Lindsey
  • <Possible follow-ups>
  • #1008 USEFOR 1.5: Suggested language on "followup", John Stanley
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Harald Tveit Alvestrand
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", John Stanley
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", John Stanley
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Seth Breidbart
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", John Stanley
  • Re: #1008 USEFOR 1.5: Suggested language on "followup", John Stanley
    • Re: #1008 USEFOR 1.5: Suggested language on "followup", Bruce Lilly
• IMAP definitions on threading, John Stanley
  • Re: IMAP definitions on threading, Harald Tveit Alvestrand
  • <Possible follow-ups>
  • Re: IMAP definitions on threading, John Stanley
    • Re: IMAP definitions on threading, Charles Lindsey
• Injection-Info issues, Charles Lindsey
  • Re: Injection-Info issues, Russ Allbery
    • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Russ Allbery
      • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Russ Allbery
      • Re: Injection-Info issues, Harald Tveit Alvestrand
      • Re: Injection-Info issues, Russ Allbery
      • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Bruce Lilly
  • Re: Injection-Info issues, Frank Ellermann
    • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Frank Ellermann
      • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Frank Ellermann
      • Re: Injection-Info issues, Frank Ellermann
      • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Frank Ellermann
      • Re: Injection-Info issues, Charles Lindsey
      • Re: Injection-Info issues, Frank Ellermann
      • Re: Injection-Info issues, Bruce Lilly
      • security considerations (was: Injection-Info issues), Frank Ellermann
      • Re: security considerations (was: Injection-Info issues), Bruce Lilly
      • Re: security considerations, Frank Ellermann
      • Re: security considerations, Bruce Lilly
      • Re: security considerations, Frank Ellermann
      • security considerations (was: Injection-Info issues), Frank Ellermann
      • Re: security considerations, Frank Ellermann
• Path header - suggested text, Charles Lindsey
  • Re: Path header - suggested text, Frank Ellermann
    • Re: Path header - suggested text, Frank Ellermann
      • Re: Path header - suggested text, Charles Lindsey
      • Re: Path header - suggested text, Henry Spencer
      • Re: Path header - suggested text, Charles Lindsey
      • Re: Path header - suggested text, Russ Allbery
    • Re: Path header - suggested text, Charles Lindsey
      • Re: Path header - suggested text, Bruce Lilly
      • Re: Path header - suggested text, Henry Spencer
      • Re: Path header - suggested text, Bruce Lilly
      • Re: Path header - suggested text, Henry Spencer
      • Re: Path header - suggested text, Bruce Lilly
      • Re: Path header - suggested text, Frank Ellermann
      • Re: Path header - suggested text, Henry Spencer
      • Re: Path header - suggested text, Bruce Lilly
      • Re: Path header - suggested text, Charles Lindsey
  • Re: Path header - suggested text, Harald Tveit Alvestrand
    • Re: Path header - suggested text, Russ Allbery
    • Re: Path header - suggested text, Charles Lindsey
• Re: #1008 USEFOR 1.5 "followup": summary so far,, John Stanley
• #1008 USEFOR 1.5 "followup": summary so far, Harald Tveit Alvestrand
  • Re: #1008 USEFOR 1.5 "followup": summary so far, Richard Clayton
    • Re: #1008 USEFOR 1.5 "followup": summary so far, Charles Lindsey
  • Re: #1008 USEFOR 1.5 "followup": summary so far, Forrest J. Cavalier III
  • Re: #1008 USEFOR 1.5 "followup": summary so far, Charles Lindsey
  • <Possible follow-ups>
  • #1008 USEFOR 1.5 "followup": summary so far, John Stanley
    • Re: #1008 USEFOR 1.5 "followup": summary so far, Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Eivind Tagseth
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Eivind Tagseth
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Ruud H.G. van Tol
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Charles Lindsey
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Seth Breidbart
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Charles Lindsey
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Seth Breidbart
    • Re: #1008 USEFOR 1.5 "followup": summary so far, Harald Tveit Alvestrand
    • Re: #1008 USEFOR 1.5 "followup": summary so far, Richard Clayton
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Charles Lindsey
      • Re: #1008 USEFOR 1.5 "followup": summary so far, Ruud H.G. van Tol
  • Re: #1008 USEFOR 1.5 "followup": summary so far, John Stanley
    • Re: #1008 USEFOR 1.5 "followup": summary so far, Ruud H.G. van Tol
  • Re: #1008 USEFOR 1.5 "followup": summary so far, John Stanley
    • IMAP definitions on threading (Re: #1008 USEFOR 1.5 "followup": summary so far), Harald Tveit Alvestrand
• New Resource: Cross-linked sections with diffs, Forrest J. Cavalier III
  • Re: New Resource: Cross-linked sections with diffs, Frank Ellermann
• Re: #1008 USEFOR 1.5: relation between a followup and a References:header?, Frank Ellermann
• #1008 USEFOR 1.5: relation between a followup and a References: header?, Harald Tveit Alvestrand
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Henry Spencer
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Richard Clayton
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Forrest J. Cavalier III
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Seth Breidbart
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Ruud H.G. van Tol
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Russ Allbery
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Eivind Tagseth
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Charles Lindsey
  • Re: #1008 USEFOR 1.5: relation between a followup and a References: he, Kai Henningsen
    • Re: #1008 USEFOR 1.5: relation between a followup and a References: he, Ruud H.G. van Tol
  • <Possible follow-ups>
  • #1008 USEFOR 1.5: relation between a followup and a References: header?, John Stanley
    • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Forrest J. Cavalier III
      • Re: #1008 USEFOR 1.5: relation between a followup and a References: header?, Charles Lindsey
• I-D ACTION:draft-ietf-usefor-usefor-04.txt, Internet-Drafts
  • Re: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Frank Ellermann
    • Re: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Harald Tveit Alvestrand
      • Re: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Frank Ellermann
    • Re: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Charles Lindsey
      • Re: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Frank Ellermann
      • Re: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Charles Lindsey
      • Misc. ABNF nits (was: I-D ACTION:draft-ietf-usefor-usefor-04.txt), Frank Ellermann
      • Re: Misc. ABNF nits (was: I-D ACTION:draft-ietf-usefor-usefor-04.txt), Charles Lindsey
      • Re: Misc. ABNF nits, Frank Ellermann
      • Re: Misc. ABNF nits, Charles Lindsey
      • Re: Misc. ABNF nits, Frank Ellermann
      • Re: Misc. ABNF nits, Henry Spencer
      • Re: Misc. ABNF nits, Frank Ellermann
      • Re: Misc. ABNF nits, Charles Lindsey
      • Re: Misc. ABNF nits, Frank Ellermann
      • Re: Misc. ABNF nits, Alexey Melnikov
      • Re: Misc. ABNF nits, Frank Ellermann
      • Re: Misc. ABNF nits, Charles Lindsey
      • RE: I-D ACTION:draft-ietf-usefor-usefor-04.txt, Scott Hollenbeck
• Poll results, membership and commitment, Harald Tveit Alvestrand
• Status request: Who's following this group?, Harald Tveit Alvestrand
  • <Possible follow-ups>
  • Re: Status request: Who's following this group?, John Stanley
• Additional WG chair for the USEFOR working group, Harald Tveit Alvestrand
  • Re: Additional WG chair for the USEFOR working group, Frank Ellermann
    • RT (Re: Additional WG chair for the USEFOR working group), Harald Tveit Alvestrand
    • Re: Additional WG chair for the USEFOR working group, Charles Lindsey

The web site for this mailing list is sponsored by the Internet Mail Consortium. If you have any suggestions for additions or corrections to this Web page, please send them to phoffman@imc.org.