Display Settings:

Format

Send to:

Choose Destination
    Proc Natl Acad Sci U S A. 2000 Mar 28;97(7):3142-7.

    Recognition of a conserved class of RNA tetraloops by Saccharomyces cerevisiae RNase III.

    Source

    Unité de Génétique des Interactions Macromoléculaires, URA1300 Centre National de la Recherche Scientifique, Département des Biotechnologies, Institut Pasteur, Paris, France. guillom@chem.ucla.edu

    Abstract

    Ribonucleases III are double-stranded RNA (dsRNA) endonucleases required for the processing of a large number of prokaryotic and eukaryotic transcripts. Although the specificity of bacterial RNase III cleavage relies on antideterminants in the dsRNA, the molecular basis of eukaryotic RNase III specificity is unknown. All substrates of yeast RNase III (Rnt1p) are capped by terminal tetraloops showing the consensus AGNN and located within 13-16 bp to Rnt1p cleavage sites. We show that these tetraloops are essential for Rnt1p cleavage and that the distance to the tetraloop is the primary determinant of cleavage site selection. The presence of AGNN tetraloops also enhances Rnt1p binding, as shown by surface plasmon resonance monitoring and modification interference studies. These results define a paradigm of RNA loops and show that yeast RNase III behaves as a helical RNA ruler that recognizes these tetraloops and cleaves the dsRNA at a fixed distance to this RNA structure. These results also indicate that proteins belonging to the same class of RNA endonucleases require different structural elements for RNA cleavage.

    PMID:
    10716739
    [PubMed - indexed for MEDLINE]
    PMCID:
    PMC16206
    Free PMC Article

    Images from this publication.See all images (4) Free text

    Figure 2
    Figure 4
    Figure 1
    Figure 3

      Supplemental Content

      Icon for HighWire Press Icon for PubMed Central

      Save items

      loading

      Recent activity

      Your browsing activity is empty.

      Activity recording is turned off.

      Turn recording back on

      See more...
      Write to the Help Desk