The Experts below are selected from a list of 13539 Experts worldwide ranked by ideXlab platform
Hideharu Amano - One of the best experts on this subject based on the ideXlab platform.
-
low latency high bandwidth Message Transfer mechanisms for a network interface plugged into a memory slot
Cluster Computing, 2002Co-Authors: Noboru Tanabe, Yoshihiro Hamada, Hironori Nakajo, Hiroaki Nishi, Tomohiro Kudoh, Junji Yamamoto, Hideharu AmanoAbstract:The communication architecture of the DIMMnet-1 network interface based on MEMOnet is described. MEMOnet is a class of a network interface plugged into a memory slot. This paper proposes three Message Transfer mechanisms named atomic on-the-fly sending (AOTF), block on-the-fly sending (BOTF) and OTF receiving with selective address translation. The DIMMnet-1 prototype will have an ASIC named Martini, two banks of PC133 based SO-DIMM slots and an 8 Gbps full duplex optical link. The software overhead incurred to generate a Message is only 1 CPU cycle and the estimated hardware delay is 105 ns using AOTF. The estimated hardware delay for receiving to on chip memory using OTF receiver is 90 ns. The estimated achievable sending bandwidth of DIMMnet-1 using BOTF is 984 MB/s which was observed in our experiments. This bandwidth is 7.4 times higher than the maximum bandwidth of PCI. This high performance is available even when simultaneous sending and receiving are executed on a cheap personal computer with DIMM slots. This paper also discribes the effects of BOTF for a PCI-based NIC.
-
on the fly sending a low latency high bandwidth Message Transfer mechanism
International Symposium on Parallel Architectures Algorithms and Networks, 2000Co-Authors: Noboru Tanabe, Yoshihiro Hamada, Hironori Nakajo, Hiroaki Nishi, Tomohiro Kudoh, Junji Yamamoto, Hideharu AmanoAbstract:Low latency high bandwidth network interface architectures are described. This paper proposes two types of architectures, atomic on-the-fly (OTF) sending with a header TLB, and block on-the-fly sending with protection stampable window memory. These techniques work very effectively with MEMOnet which is a class of network interface card (NIC) plugged into a memory slot. We are developing a network interface controller LSI called Martini. The Martini chip is used in two prototype network interface cards, DIMMnet-I based on MEMOnet, and RHiNET-2/NI based on PCI. On a DIMMnet-I, the software overhead needed to generate a Message is only 1 CPU cycle and the estimated hardware delay is less than 100 ns using atomic OTF sending. The estimated achievable sending bandwidth of DIMMnet-I using block OTF sending is 984 MB/s which was observed in our experiments. This bandwidth is 7.4 times higher than the maximum bandwidth of PCI. This excellent performance is available for cheap personal computers with DIMM slots. This paper also describes the effects of block OTF sending for a PCI-based NIC.
G. Vaudreuil - One of the best experts on this subject based on the ideXlab platform.
-
An Extensible Message Format for Delivery Status Notifications", RFC 3464
2003Co-Authors: K Moore, G. VaudreuilAbstract:draft-ietf-notary-mime-delivery-05.txt Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt " listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail. Because many Messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "LAN-based " systems), the DSN protocol is designed to be useful in a multi-protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign " addresses and error codes, in addition to those normally used in Internet mail. Additional attributes may also be defined to support "tunneling " of foreign notifications through Internet mail
-
An Extensible Message Format for Delivery Status Notifications", RFC 3464
2003Co-Authors: K Moore, G. VaudreuilAbstract:draft-ietf-notary-mime-delivery-02.txt Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet Drafts as reference material or to cite them other than as a "work in progress". This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or inter-network mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is meant to be a machine-processable alternative to the full range of electronic mail delivery status notifications currently in use in the Internet. 1
-
An Extensible Message Format for Delivery Status Notifications", RFC 3464
2003Co-Authors: K Moore, G. VaudreuilAbstract:This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. This memo defines a Multipurpose Internet Mail Extensions (MIME) content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail
-
An Extensible Message Format for Delivery Status Notifications", Internet-Draft draft-vaudreuil-rfc1894bis-00.txt (work in progress
2001Co-Authors: K Moore, G. VaudreuilAbstract:draft-ietf-notary-mime-delivery-05.txt Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt " listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail. Because many Messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "LAN-based " systems), the DSN protocol is designed to be useful in a multi-protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign " addresses and error codes, in addition to those normally used in Internet mail. Additional attributes may also be defined to support "tunneling " of foreign notifications through Internet mail
-
an extensible Message format for delivery status notifications
RFC, 1996Co-Authors: K Moore, G. VaudreuilAbstract:This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail.
Nen-fu Huang - One of the best experts on this subject based on the ideXlab platform.
-
Providing multicast short Message services over self-routing mobile cellular backbone network
IEEE Transactions on Vehicular Technology, 2003Co-Authors: Nen-fu HuangAbstract:The short Message service (SMS), a bidirectional service for short alphanumeric (up to 160 bytes) Messages, is a unique feature of GSM not found in older analog systems. Multireceiver short Message traffic has increased amazingly over the years. We propose a multicast SMS architecture over our backbone network. Then, we demonstrate some approaches to maintain the SMS center location information consistent with the home location register and illustrate our scheme for mobile terminated short Message Transfer. Finally, we simulate and evaluate this architecture. Our simulation indicates that the proposed strong consistency approaches have optimal efficiency by adjusting parameters, and the proposed architecture efficiently provides self-routing capability and multicast functionality in our cellular backbone network. The study also provides a further insight on the issues of multicast wireless cellular backbone network and demonstrates a referable methodology to propose and analyze a multicast cellular backbone network, which can promote the technology of a personal communication network.
-
Providing multicast short Message services over self-routing mobile cellular backbone network
GLOBECOM'01. IEEE Global Telecommunications Conference (Cat. No.01CH37270), 2001Co-Authors: Nen-fu HuangAbstract:The short Message service (SMS), a bidirectional service for short alphanumeric (up to 160 bytes) Messages, is a unique feature of GSM, not found in older analog systems. We propose a multicast short Message service architecture over a backbone network. We demonstrate some approaches to maintain the location information of the short Message service center consistent to the home location register and illustrate our scheme for mobile-terminated short Message Transfer. Finally, we simulate and evaluate this architecture. Our simulation indicates that the proposed strong consistency approach has optimal efficiency by adjusting parameters. Also, the proposed architecture efficiently provides a self-routing capability and multicast functionality in the cellular backbone network. This study also provides a further insight on the issues of a multicast wireless cellular backbone network and demonstrates a referable methodology to propose and analyze a multicast cellular backbone network, which can promote the technology of personal communication networks.
Noboru Tanabe - One of the best experts on this subject based on the ideXlab platform.
-
low latency high bandwidth Message Transfer mechanisms for a network interface plugged into a memory slot
Cluster Computing, 2002Co-Authors: Noboru Tanabe, Yoshihiro Hamada, Hironori Nakajo, Hiroaki Nishi, Tomohiro Kudoh, Junji Yamamoto, Hideharu AmanoAbstract:The communication architecture of the DIMMnet-1 network interface based on MEMOnet is described. MEMOnet is a class of a network interface plugged into a memory slot. This paper proposes three Message Transfer mechanisms named atomic on-the-fly sending (AOTF), block on-the-fly sending (BOTF) and OTF receiving with selective address translation. The DIMMnet-1 prototype will have an ASIC named Martini, two banks of PC133 based SO-DIMM slots and an 8 Gbps full duplex optical link. The software overhead incurred to generate a Message is only 1 CPU cycle and the estimated hardware delay is 105 ns using AOTF. The estimated hardware delay for receiving to on chip memory using OTF receiver is 90 ns. The estimated achievable sending bandwidth of DIMMnet-1 using BOTF is 984 MB/s which was observed in our experiments. This bandwidth is 7.4 times higher than the maximum bandwidth of PCI. This high performance is available even when simultaneous sending and receiving are executed on a cheap personal computer with DIMM slots. This paper also discribes the effects of BOTF for a PCI-based NIC.
-
on the fly sending a low latency high bandwidth Message Transfer mechanism
International Symposium on Parallel Architectures Algorithms and Networks, 2000Co-Authors: Noboru Tanabe, Yoshihiro Hamada, Hironori Nakajo, Hiroaki Nishi, Tomohiro Kudoh, Junji Yamamoto, Hideharu AmanoAbstract:Low latency high bandwidth network interface architectures are described. This paper proposes two types of architectures, atomic on-the-fly (OTF) sending with a header TLB, and block on-the-fly sending with protection stampable window memory. These techniques work very effectively with MEMOnet which is a class of network interface card (NIC) plugged into a memory slot. We are developing a network interface controller LSI called Martini. The Martini chip is used in two prototype network interface cards, DIMMnet-I based on MEMOnet, and RHiNET-2/NI based on PCI. On a DIMMnet-I, the software overhead needed to generate a Message is only 1 CPU cycle and the estimated hardware delay is less than 100 ns using atomic OTF sending. The estimated achievable sending bandwidth of DIMMnet-I using block OTF sending is 984 MB/s which was observed in our experiments. This bandwidth is 7.4 times higher than the maximum bandwidth of PCI. This excellent performance is available for cheap personal computers with DIMM slots. This paper also describes the effects of block OTF sending for a PCI-based NIC.
K Moore - One of the best experts on this subject based on the ideXlab platform.
-
An Extensible Message Format for Delivery Status Notifications", RFC 3464
2003Co-Authors: K Moore, G. VaudreuilAbstract:draft-ietf-notary-mime-delivery-05.txt Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt " listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail. Because many Messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "LAN-based " systems), the DSN protocol is designed to be useful in a multi-protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign " addresses and error codes, in addition to those normally used in Internet mail. Additional attributes may also be defined to support "tunneling " of foreign notifications through Internet mail
-
An Extensible Message Format for Delivery Status Notifications", RFC 3464
2003Co-Authors: K Moore, G. VaudreuilAbstract:draft-ietf-notary-mime-delivery-02.txt Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet Drafts as reference material or to cite them other than as a "work in progress". This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or inter-network mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is meant to be a machine-processable alternative to the full range of electronic mail delivery status notifications currently in use in the Internet. 1
-
An Extensible Message Format for Delivery Status Notifications", RFC 3464
2003Co-Authors: K Moore, G. VaudreuilAbstract:This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. This memo defines a Multipurpose Internet Mail Extensions (MIME) content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail
-
An Extensible Message Format for Delivery Status Notifications", Internet-Draft draft-vaudreuil-rfc1894bis-00.txt (work in progress
2001Co-Authors: K Moore, G. VaudreuilAbstract:draft-ietf-notary-mime-delivery-05.txt Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt " listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail. Because many Messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "LAN-based " systems), the DSN protocol is designed to be useful in a multi-protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign " addresses and error codes, in addition to those normally used in Internet mail. Additional attributes may also be defined to support "tunneling " of foreign notifications through Internet mail
-
an extensible Message format for delivery status notifications
RFC, 1996Co-Authors: K Moore, G. VaudreuilAbstract:This memo defines a MIME content-type that may be used by a Message Transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a Message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail.