ietf-openproxy
[Top] [All Lists]

RE: OCP transport nomination

2003-05-05 13:20:50

Please show me how to use the URI to find the document.  I can use it to
find "404", but then, lots of things can find "404".

 On Mon, 5 May 2003, The Purple Streak, Hilarie Orman wrote:
 > Where is the definition of the TLS profile for BEEP?
 See RFC 3080 (Sections 3.1 and 7.2, at least):
         <profile uri="http://xml.resource.org/profiles/TLS";>
            <ready />
         </profile>

In this message you referred to "the MIT license"; what did you mean?

  From: Alex Rousskov <rousskov(_at_)measurement-factory(_dot_)com>
  To: ietf-openproxy(_at_)imc(_dot_)org
  Subject: Re: BEEP as OCP transport
  Date: Thu, 17 Apr 2003 12:22:09 -0600 (MDT)
  In-Reply-To: 
<20030417102820(_dot_)064ae9ed(_dot_)mrose(_at_)dbc(_dot_)mtview(_dot_)ca(_dot_)us>
  Message-ID: 
<Pine(_dot_)BSF(_dot_)4(_dot_)53(_dot_)0304171132590(_dot_)31225(_at_)measurement-factory(_dot_)com>


 > There have been alllusions to XML licensing issues.  What are they?

 I am not aware of any; can you be more specific? If BEEP (an IETF
 protocol) uses XML, we should be safe to do so, I guess.





<Prev in Thread] Current Thread [Next in Thread>