SAM4
"Eddy Quicksall" <[email protected]> Thu, 7 Aug 2008 16:06:20 -0400
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============1743623968== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C8F8A7.87B98B50" This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C8F8A7.87B98B50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Is there any plan to support SAM4? What I'm interested in is the new = TMF's in SAM4. Eddy ------=_NextPart_000_0015_01C8F8A7.87B98B50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.6000.16674" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>Is there any plan to support SAM4? What I'm = interested in is=20 the new TMF's in SAM4.</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>Eddy</FONT></DIV></BODY></HTML> ------=_NextPart_000_0015_01C8F8A7.87B98B50-- --===============1743623968== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list [email protected] https://www.ietf.org/mailman/listinfo/ips --===============1743623968==--