UNITED STATES INTERNATTONAL TRADE CGMIVHSSION
`
`WASESGTON. D.C.
`
`Administrative Law Judge
`
`
`Before the Honorable E. James Gildea
`
`In the Matter of:
`
`{
`
`CERTAIN DEVICES WITH SECURE
`COMNIUNICATION CAPABILITIES,
`COEHONENTS THEREOF, AND
`PRODUCTS CONTAEEING TE SANIE
`
`
`Investigation No. 337—TA-858
`
`DECLARATION OF THE RFC PUBLISHER FOR Tfl INTERNET ENGINEERING
`
`TASK FORCE, AN ORGANIZED ACTIVITY OF THE INTERNET SOCIETY
`
`1, Sandy Ginoza, of lawful age, based on my personal knowledge and information, hereby
`
`declare:
`
`1.
`
`Iarn an employee of Association Management Solutions, LLC (“AMS”), which
`
`acts under contract to the Internet Society (“ISOC”) as the operator of the RFC Pubiisher. The
`
`RFC Publisher is part of the “RFC Editor” fimction, which provides online access to the
`
`authoritative Request for Comments (“RFC”) series of documents (“RFC Series”), and provides
`
`storage and preservation of records relating to these documents. The RFC Series includes,
`
`among other things, the series of Internet standards developed by the Internet Engineering Task
`
`Force (“ETF”), an organized activity of ISOC. I hold the position of Director of the RFC
`
`Publisher. I began employment with AMS in this capacity on 5 January 2010.
`
`2.
`
`Among my responsibilities as Director of the RFC Publisher, I act as the
`
`custodian of records relating to the RFC Series.
`
`Petitioner Apple Inc. - Exhibit 1060, p. l
`
`Petitioner Apple Inc. - Exhibit 1060, p. 1
`
`
`
`WASESGTON. D.C.
`
`Administrative Law Judge
`
`
`Before the Honorable E. James Gildea
`
`In the Matter of:
`
`{
`
`CERTAIN DEVICES WITH SECURE
`COMNIUNICATION CAPABILITIES,
`COEHONENTS THEREOF, AND
`PRODUCTS CONTAEEING TE SANIE
`
`
`Investigation No. 337—TA-858
`
`DECLARATION OF THE RFC PUBLISHER FOR Tfl INTERNET ENGINEERING
`
`TASK FORCE, AN ORGANIZED ACTIVITY OF THE INTERNET SOCIETY
`
`1, Sandy Ginoza, of lawful age, based on my personal knowledge and information, hereby
`
`declare:
`
`1.
`
`Iarn an employee of Association Management Solutions, LLC (“AMS”), which
`
`acts under contract to the Internet Society (“ISOC”) as the operator of the RFC Pubiisher. The
`
`RFC Publisher is part of the “RFC Editor” fimction, which provides online access to the
`
`authoritative Request for Comments (“RFC”) series of documents (“RFC Series”), and provides
`
`storage and preservation of records relating to these documents. The RFC Series includes,
`
`among other things, the series of Internet standards developed by the Internet Engineering Task
`
`Force (“ETF”), an organized activity of ISOC. I hold the position of Director of the RFC
`
`Publisher. I began employment with AMS in this capacity on 5 January 2010.
`
`2.
`
`Among my responsibilities as Director of the RFC Publisher, I act as the
`
`custodian of records relating to the RFC Series.
`
`Petitioner Apple Inc. - Exhibit 1060, p. l
`
`Petitioner Apple Inc. - Exhibit 1060, p. 1
`
`
`
`3.-
`
`From June 1999 to 4 January 2010, I was an employee of the Information
`
`Sciences Institute at the University of Southern California (‘‘ISI“). 1 held various position titles
`
`with the RFC Editor project at ISI, ending with Senior Editor.
`
`4.
`
`The RFC Editor function was conducted by ISI under contract to the United
`
`States government prior to 1998. In 1998, ISOC, in furtherance of its IETF activity, entered into
`
`the first in a series of contracts with IS} providing for iSI‘s performance of the RFC Editor
`
`f|.1IlCfl0I1. Beginning in 2010, certain aspects of the RFC Editor function were assumed by the
`
`RFC Publisher operation of AMS under contract to {SOC (acting through its IETF function and,
`
`in particular, the IETF Administrative Oversight Committee). The business records of the RFC
`
`Editor function as it was conducted by ISI are currently housed on the computer systems of AMS,
`
`as a contractor to ISOC.
`
`5.
`
`I make this Declaration based on my personai knowledge and information
`
`contained in the business records of the RFC editor as they are currently housed at AMS, or
`
`confirmation with other responsible RFC Editor personnel with such knowledge. If called as a
`
`witness in this Investigation, I could and would testify to the facts as stated in this Declaration.
`
`6.
`
`The document produced as Bates number 337-TA-858-IETFOOOOI-00021 is a
`
`true and correct copy of RFC 1033.
`
`7.
`
`I hereby certify that the produced RFC 1033 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 2
`
`Petitioner Apple Inc. - Exhibit 1060, p. 2
`
`
`
`8.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1033 in the ordinary course of its regularly conducted activities. RFC
`
`1033 has been publicly available through the RFC Editor’s web site or through other means since
`
`its publication in November 1987.
`
`9.
`
`The document produced as Bates number 337-TA—858-ETF00O22~0O073 is a
`
`true and correct copy of RFC 1034.
`
`10.
`
`I hereby certify that the produced RFC 1034 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`11.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1034 in the ordinary course of its regularly conducted activities. RFC
`
`1034 has been publicly avaiiable through the RFC Editor’s web site or through other means since
`
`its publication in November 1987.
`
`12.
`
`The document produced as Bates number 337-"EA-858-IETFO0074-00125 is a
`
`true and correct copy of RFC 1035.
`
`13.
`
`I hereby certify that the produced RFC 1035 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 3
`
`Petitioner Apple Inc. - Exhibit 1060, p. 3
`
`
`
`14.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1035 in the ordinary course of its regularly conducted activities. RFC
`
`1035 has been publicly available through the RFC Editor’s web site or through other means since
`
`its publication in November 1987.
`
`15.
`
`The document produced as Bates number 337-TA-858-IETF00126—O024O is a
`
`true and correct copy of RFC 1122.
`
`16.
`
`I hereby certify that the produced RFC 1122 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`17.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1122 in the ordinary course of its regularly conducted activities. RFC
`
`1122 has been publicly available through the RFC Editor’s web site or through other means since
`
`its publication in October 1989.
`
`18.
`
`The document produced as Bates number 337-TA—858-IETF00241-00337 is a
`
`true and correct copy of RFC 1123.
`
`19.
`
`I hereby certify that the produced RFC 1123 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 4
`
`Petitioner Apple Inc. - Exhibit 1060, p. 4
`
`
`
`20.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1123 in the ordinary course of its regularly conducted activities. RFC
`
`1123 has been publicly available through the RFC Editor’s web site or through other means since
`
`its publication in October 1989.
`
`21.
`
`The document produced as Bates number 337—TA—858—IE’1‘F00338-00344 is a
`
`true and correct copy of RFC 1591.
`
`22.
`
`I hereby certify that the produced RFC 1591 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and ((3) made by the regularly
`
`conducted activity as a regular practice.
`
`23.
`
`Based on a Search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1591 in the ordinary course of its regularly conducted activities. RFC
`
`1591 has been publicly available through the RFC Editofs web site or through other means since
`
`its publication in March 1994.
`
`24.
`
`The document produced as Bates number 337-TA-858-IETFO0345-003 54 is a
`
`true and correct copy of RFC 1631.
`
`25.
`
`I hereby certify that the produced RFC 1631 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 5
`
`Petitioner Apple Inc. - Exhibit 1060, p. 5
`
`
`
`26.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1631 in the ordinary course of its regularly conducted activities.
`
`RFC 1631 has been publicly available through the RFC Bditor’s web site or through other means
`
`since its publication in May 1994.
`
`27.
`
`The document produced as Bates number 337-TA-858-ETF00355-00403 is a
`
`true and correct copy of RFC 1636.
`
`28.
`
`I hereby certify that the produced RFC 1636 constitutes a record of reguiarly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regutarly
`
`conducted activity as a regular practice.
`
`29.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1636 in the ordinary course of its regularly conducted activities.
`
`RFC 1636 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in June 1994.
`
`30.
`
`The document produced as Bates number 337-TA—858-IETF00404-00453 is a
`
`true and correct copy of RFC 1661.
`
`3 l.
`
`I hereby certify that the produced RFC 1661 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regutar practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 6
`
`Petitioner Apple Inc. - Exhibit 1060, p. 6
`
`
`
`32.
`
`Based on a search ofRFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1661 in the ordinary course of its regularly conducted activities.
`
`RFC 1661 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in July 1994.
`
`33.
`
`The document produced as Bates number 337-TA-858-[ETFO0454-00477 is a
`
`true and correct copy of RFC 1738.
`
`34.
`
`I hereby certify that the produced RFC 1738 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`35.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1738 in the ordinary course of its regularly conducted activities.
`
`RFC 1738 has been publiciy available through the RFC Editor’s web site or through other means
`
`since its publication in December 1994.
`
`36.
`
`The document produced as Bates number 337«TA~858-IETF00478~00498 is a
`
`true and correct copy of RFC 1825.
`
`37.
`
`I hereby certify that the produced RFC 1825 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a reguiar practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 7
`
`Petitioner Apple Inc. - Exhibit 1060, p. 7
`
`
`
`38.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1825 in the ordinary course of its regularly conducted activities.
`
`RFC 1825 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in August 1995.
`
`39.
`
`The document produced as Bates number 337-TA-858-ETF00499-—0O5ll is a
`
`true and correct copy of RFC 1826.
`
`40.
`
`I hereby certify that the produced RFC 1826 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`41.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1826 in the ordinary course of its regularly conducted activities.
`
`RFC 1826 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in August 1995.
`
`42.
`
`The document produced as Bates number 337-TA-858-IETFOO5 l 2-00523 is a
`
`true and correct copy of RFC 1827.
`
`43.
`
`I hereby certify that the produced RFC 1827 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 8
`
`Petitioner Apple Inc. - Exhibit 1060, p. 8
`
`
`
`44.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1827 in the ordinary course of its regularly conducted activities.
`
`RFC 1827 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in August 1995.
`
`45.
`
`The document produced as Bates number 337-TA-858—IE’I"FO0524—00529 is a
`
`true and correct copy of RFC 1828.
`
`46.
`
`I hereby certify that the produced RFC 1828 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a reguiar practice.
`
`47.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1828 in the ordinary course of its regularly conducted activities.
`
`RFC 1828 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in August 1995.
`
`48.
`
`The document produced as Bates number 337~TA—858—IETFOO530-00540 is a
`
`true and correct copy of RFC 1829.
`
`49.
`
`I hereby certify that the produced RFC 1829 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`Petitioner Apple Inc. - Exhibit 1060, p. 9
`
`Petitioner Apple Inc. - Exhibit 1060, p. 9
`
`
`
`50.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1829 in the ordinary course of its regularly conducted activities.
`
`RFC 1829 has been pubiicly available through the RFC Editor’s web site or through other means
`
`since its publication in August 1995-
`
`51.
`
`The document produced as Bates number 337-TA-858-IETFO0541~0O61l is a
`
`true and correct copy of RFC 1889.
`
`52.
`
`I hereby certify that the produced RFC 1889 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice-
`
`53.
`
`Based on a Search of RF C Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1889 in the ordinary course of its reguiarly conducted activities.
`
`RFC 1889 has been pubticly avaiiabie through the RFC Editor’s web site or through other means
`
`since its publication in January 1996.
`
`54.
`
`The document produced as Bates number 33 7-TA-858-ETFOO612-00628 is a
`
`true and correct copy of RFC 1890.
`
`55.
`
`I hereby certify that the produced RFC 1890 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`1f\
`
`Petitioner Apple Inc. - Exhibit 1060, p. 10
`
`Petitioner Apple Inc. - Exhibit 1060, p. 10
`
`
`
`56.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1890 in the ordinary course of its regularly conducted activities.
`
`RFC 1890 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in January 1996.
`
`57.
`
`The document produced as Bates number 337-TA—858—IETFOO629-00637 is a
`
`true and correct copy of RFC 1918.
`
`58.
`
`I hereby certify that the produced RFC 1918 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`59.
`
`Based on a search ofRFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1918 in the ordinary course of its regularly conducted activities.
`
`RFC 1918 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in February 1996.
`
`60.
`
`The document produced as Bates number 337-TA-858-IETF0063 8-00646 is a
`
`true and correct copy of RFC 1928.
`
`61.
`
`I hereby certify that the produced RFC 1928 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`11
`
`Petitioner Apple Inc. - Exhibit 1060, p. 11
`
`Petitioner Apple Inc. - Exhibit 1060, p. 11
`
`
`
`62.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1928 in the ordinary course of its regularly conducted activities.
`
`RFC 1928 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in March 1996.
`
`63.
`
`The document produced as Bates number 337~TA-858—IETF00647-00703 is a
`
`true and correct copy of RFC 1945.
`
`64.
`
`I hereby certify that the produced RFC 1945 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`65.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1945 in the ordinary course of its regularly conducted activities.
`
`RFC 1945 has been publicly available through the R‘iiC Editor's web site or through other means
`
`since its publication in May 1996.
`
`66.
`
`The document produced as Bates number 337~TA-858-—IETF00704~007l4 is a
`
`true and correct copy of RFC 1968.
`
`67.
`
`I hereby certify that the produced RFC 1968 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`1'1
`
`Petitioner Apple Inc. - Exhibit 1060, p. 12
`
`Petitioner Apple Inc. - Exhibit 1060, p. 12
`
`
`
`68.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 1968 in the ordinary course of its regularly conducted activities.
`
`RFC 1968 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in June 1996.
`
`69.
`
`The document produced as Bates number 337—TA-858-IETFOO715-00724 is a
`
`true and correct copy of RFC 2052.
`
`70.
`
`I hereby certify that the produced RFC 2052 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`71.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2052 in the ordinary course of its regularly conducted activities.
`
`RFC 2052 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in October 1996.
`
`72.
`
`The document produced as Bates number 337-TA-858-IETF00725-00763 is a
`
`hue and correct copy of RFC 2065.
`
`73.
`
`I hereby certify that the produced RFC 2065 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowiedge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`1’!
`
`Petitioner Apple Inc. - Exhibit 1060, p. 13
`
`Petitioner Apple Inc. - Exhibit 1060, p. 13
`
`
`
`74.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2065 in the ordinary course of its regularly conducted activities.
`
`RFC 2065 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in January 1997.
`
`75.
`
`The document produced as Bates number 337-TA-858-IETFOO764—00806 is a
`
`true and correct copy of RFC 2131.
`
`76.
`
`I hereby certify that the produced RFC 2131 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by; or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`77.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2131 in the ordinary course of its regularly conducted activities.
`
`RFC 2131 has been pubiicly available through the RFC Editor’s web site or through other means
`
`since its publication in March 1997.
`
`78.
`
`The document produced as Bates number 337-TA-858-IETFOOSO7-00867 is a
`
`true and correct copy of RFC 2138.
`
`79.
`
`I hereby certify that the produced RFC 2138 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`‘IA
`
`Petitioner Apple Inc. - Exhibit 1060, p. 14
`
`Petitioner Apple Inc. - Exhibit 1060, p. 14
`
`
`
`80.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2138 in the ordinary course of its regularly conducted activities.
`
`RFC 2138 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in April 1997.
`
`81.
`
`The document produced as Bates number 337-TA-858-IETFO0868-00879 is a
`
`true and correct copy of RFC 2t90.
`
`82.
`
`I hereby certify that the produced RFC 2190 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence ofthe
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`rnatters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice-
`
`83.
`
`Based on a Search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2190 in the ordinary course of its regularly conducted activities.
`
`RFC 2190 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in September 1997.
`
`84.
`
`The document produced as Bates number 337—TA—858-IETFO0880~00890 is a
`
`true and correct copy of RFC 2230.
`
`85.
`
`I hereby certify that the produced RFC 2230 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course ofthe regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`‘I-C
`
`Petitioner Apple Inc. - Exhibit 1060, p. 15
`
`Petitioner Apple Inc. - Exhibit 1060, p. 15
`
`
`
`86.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2230 in the ordinary course of its regularly conducted activities.
`
`RFC 2230 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in November 1997.
`
`87.
`
`The document produced as Bates number 337—TA-858-IETF0089l-00965 is a
`
`true and correct copy of RFC 2246.
`
`88.
`
`I hereby certify that the produced RFC 2246 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`89.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2246 in the ordinary course of its regularly conducted activities.
`
`RFC 2246 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in January 1999.
`
`90.
`
`The document produced as Bates number 337-TA-858-IETFO0966-00972 is a
`
`true and correct copy of RFC 2247.
`
`91.
`
`I hereby certify that the produced RFC 2247 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`1C
`
`Petitioner Apple Inc. - Exhibit 1060, p. 16
`
`Petitioner Apple Inc. - Exhibit 1060, p. 16
`
`
`
`92.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2247 in the ordinary course of its regularly conducted activities.
`
`RFC 2247 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in January 1998.
`
`93.
`
`The document produced as Bates number 337—TA-858~IETF00973-00987 is a
`
`true and correct copy of RFC 2250.
`
`94.
`
`I hereby certify that the produced RFC 2250 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`95.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2250 in the ordinary course of its regularly conducted activities.
`
`RFC 2250 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in January 1998.
`
`96.
`
`The document produced as Bates number 337—TA-858—H3TF00988—0lO73 is a
`
`true and correct copy of RFC 2326.
`
`97.
`
`I hereby certify that the produced RFC 2326 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`1''!
`
`Petitioner Apple Inc. - Exhibit 1060, p. 17
`
`Petitioner Apple Inc. - Exhibit 1060, p. 17
`
`
`
`98.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 23 26 in the ordinary course of its reguiarly conducted activities.
`
`RFC 2326 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in April 1998.
`
`99.
`
`The document produced as Bates number 337-TA-858-IETFOtO74—0l1l3 is a
`
`true and correct copy of RFC 2327.
`
`100.
`
`I hereby certify that the produced RFC 2327 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`101. Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2327 in the ordinary course of its regularly conducted activities.
`
`RFC 2327 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in April 1998.
`
`102.
`
`The document produced as Bates number 33 7-TA-858-ETF01 I 14-01 121 is a
`
`true and correct copy of RFC 2343.
`
`103.
`
`I hereby certify that the produced RFC 2343 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowledge of those
`
`matters; B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`‘IO
`
`Petitioner Apple Inc. - Exhibit 1060, p. 18
`
`Petitioner Apple Inc. - Exhibit 1060, p. 18
`
`
`
`104.
`
`Based on a search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2343 in the ordinary course of its reguiarly conducted activities.
`
`RFC 2343 has been publicly available through the RFC Editor’s web site or through other means
`
`since its publication in May 1998.
`
`105.
`
`The document produced as Bates number 337-TA-858-IETF011Z2~01 183 is a
`
`true and correct copy of RFC 2401.
`
`106.
`
`I hereby certify that the produced RFC 2401 constitutes a record of regularly
`
`conducted business activity which was (A) made at or near the time of the occurrence of the
`
`matters set forth by, or from information transmitted by, a person with knowiedge of those
`
`matters; (B) kept in the course of the regularly conducted activity; and (C) made by the regularly
`
`conducted activity as a regular practice.
`
`107. Based on a Search of RFC Editor records, I have determined that the RFC Editor
`
`maintained a copy of RFC 2401 in the ordinary course of its regularly conducted activities.
`
`RFC 2401 has been publicly available through the RFC Editor’s web site or through other means
`
`since its pubiication i
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
